lighthouseResult
requestedUrl: https://gf.dev/toolbox
finalUrl: https://gf.dev/toolbox
lighthouseVersion: 6.0.0
userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/83.0.4103.93 Safari/537.36
fetchTime: 2020-06-24T18:39:31.794Z
networkUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3963.0 Safari/537.36 Chrome-Lighthouse
hostUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/83.0.4103.93 Safari/537.36
benchmarkIndex: 656
emulatedFormFactor: desktop
locale: en-US
onlyCategories: performance
channel: lr
runWarnings (print_r): Array
(
)
1
AUDITS
uses-long-cache-ttl
numericValue: 278045.86666667
id: uses-long-cache-ttl
title: Serve static assets with an efficient cache policy
description: A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl).
score: 0.26
scoreDisplayMode: numeric
displayValue: 12 resources found
first-meaningful-paint
id: first-meaningful-paint
title: First Meaningful Paint
description: First Meaningful Paint measures when the primary content of a page is visible. [Learn more](https://web.dev/first-meaningful-paint).
score: 0.91
scoreDisplayMode: numeric
displayValue: 0.9 s
numericValue: 919
network-server-latency
id: network-server-latency
title: Server Backend Latencies
description: Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. [Learn more](https://hpbn.co/primer-on-web-performance/#analyzing-the-resource-waterfall).
score:
scoreDisplayMode: informative
displayValue: 0 ms
numericValue: 0
type: table
items (print_r): Array
(
)
1
headings (print_r): Array
(
)
1
cumulative-layout-shift
id: cumulative-layout-shift
title: Cumulative Layout Shift
description: Cumulative Layout Shift measures the movement of visible elements within the viewport. [Learn more](https://web.dev/cls).
score: 1
scoreDisplayMode: numeric
displayValue: 0.002
numericValue: 0.0016302530426407
third-party-summary
id: third-party-summary
title: Minimize third-party usage
description: Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. [Learn more](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/loading-third-party-javascript/).
score: 1
scoreDisplayMode: binary
displayValue: Third-party code blocked the main thread for 0 ms
Data items: text: Hotjar url: https://www.hotjar.com/ type: link mainThreadTime: 106.996 transferSize: 79257 blockingTime: 0
Data items: text: Google Tag Manager url: https://marketingplatform.google.com/about/tag-manager/ type: link mainThreadTime: 21.253 transferSize: 34165 blockingTime: 0
Data items: text: Google Analytics url: https://www.google.com/analytics/analytics/ type: link mainThreadTime: 55.579 transferSize: 19819 blockingTime: 0
type: table
wastedBytes: 133241
wastedMs: 0
text: Third-Party
itemType: link
key: entity
key: transferSize
text: Transfer Size
granularity: 1
itemType: bytes
key: blockingTime
text: Main-Thread Blocking Time
granularity: 1
itemType: ms
timing-budget
id: timing-budget
title: Timing budget
description: Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
score:
scoreDisplayMode: notApplicable
render-blocking-resources
id: render-blocking-resources
title: Eliminate render-blocking resources
description: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources).
score: 0.87
scoreDisplayMode: numeric
displayValue: Potential savings of 160 ms
numericValue: 155
type: opportunity
overallSavingsMs: 155
Data items: totalBytes: 3654 url: https://gf.dev/cdn-cgi/apps/head/R9DXFE1q191siYemwiSr1hjmjk0.js wastedMs: 150
Data items: totalBytes: 32233 url: https://gf.dev/static/css/all.min.css wastedMs: 110
heading items: label: URL valueType: url key: url
heading items: label: Transfer Size valueType: bytes key: totalBytes
main-thread-tasks
id: main-thread-tasks
title: Tasks
description: Lists the toplevel main thread tasks that executed during page load.
score:
scoreDisplayMode: informative
type: table
heading items: text: Start Time key: startTime itemType: ms granularity: 1
heading items: text: End Time key: duration itemType: ms granularity: 1
data items: startTime: 226.838 duration: 12.937
data items: startTime: 314.06 duration: 7.147
data items: startTime: 351.572 duration: 7.383
data items: startTime: 360.219 duration: 11.46
data items: startTime: 371.905 duration: 14.504
data items: startTime: 388.38 duration: 46.156
data items: startTime: 447.504 duration: 76.083
data items: startTime: 540.751 duration: 9.548
data items: startTime: 556.192 duration: 55.344
data items: startTime: 611.589 duration: 8.982
data items: startTime: 948.253 duration: 41.392
data items: startTime: 989.665 duration: 9.572
data items: startTime: 1008.012 duration: 36.963
data items: startTime: 1045.009 duration: 44.69
data items: startTime: 1089.906 duration: 6.372
data items: startTime: 1111.166 duration: 29.911
data items: startTime: 1185.623 duration: 20.127
data items: startTime: 1205.825 duration: 5.939
speed-index
id: speed-index
title: Speed Index
description: Speed Index shows how quickly the contents of a page are visibly populated. [Learn more](https://web.dev/speed-index).
score: 1
scoreDisplayMode: numeric
displayValue: 0.6 s
numericValue: 576.40797016943
network-rtt
id: network-rtt
title: Network Round Trip Times
description: Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. [Learn more](https://hpbn.co/primer-on-latency-and-bandwidth/).
score:
scoreDisplayMode: informative
displayValue: 0 ms
numericValue: 0
max-potential-fid
id: max-potential-fid
title: Max Potential First Input Delay
description: The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more](https://web.dev/lighthouse-max-potential-fid).
score: 0.99
scoreDisplayMode: numeric
displayValue: 80 ms
numericValue: 76
mainthread-work-breakdown
id: mainthread-work-breakdown
title: Minimizes main-thread work
description: Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn more](https://web.dev/mainthread-work-breakdown)
score: 1
scoreDisplayMode: numeric
displayValue: 0.5 s
numericValue: 549.647
screenshot-thumbnails
id: screenshot-thumbnails
title: Screenshot Thumbnails
description: This is what the load of your site looked like.
score:
scoreDisplayMode: informative
id: user-timings
title: User Timing marks and measures
description: Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. [Learn more](https://web.dev/user-timings).
score:
scoreDisplayMode: notApplicable
type: table
id: network-requests
title: Network Requests
description: Lists the network requests that were made during page load.
score:
scoreDisplayMode: informative
first-contentful-paint:
id: first-contentful-paint
title: First Contentful Paint
description: First Contentful Paint marks the time at which the first text or image is painted. [Learn more](https://web.dev/first-contentful-paint).
score: 1
scoreDisplayMode: numeric
displayValue: 0.4 s
numericValue: 395
unused-css-rules:
id: unused-css-rules
title: Remove unused CSS
description: Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. [Learn more](https://web.dev/unused-css-rules).
score: 1
scoreDisplayMode: numeric
displayValue: Potential savings of 40 KB
numericValue: 0
interactive:
id: interactive
title: Time to Interactive
description: Time to interactive is the amount of time it takes for the page to become fully interactive. [Learn more](https://web.dev/interactive).
score: 1
scoreDisplayMode: numeric
displayValue: 1.3 s
numericValue: 1280.5
critical-request-chains:
id: critical-request-chains
title: Avoid chaining critical requests
description: The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. [Learn more](https://web.dev/critical-request-chains).
score:
scoreDisplayMode: informative
displayValue: 7 chains found
longestChain transferSize: 2691
longestChain duration: 1046.5170000098
longestChain length: 1
type: criticalrequestchain
final-screenshot:
id: final-screenshot
title: Final Screenshot
description: The last screenshot captured of the pageload.
score:
scoreDisplayMode: informative
offscreen-images:
id: offscreen-images
title: Defer offscreen images
description: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images).
score: 1
scoreDisplayMode: numeric
numericValue: 0
largest-contentful-paint:
id: largest-contentful-paint
title: Largest Contentful Paint
description: Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint)
score: 0.91
scoreDisplayMode: numeric
displayValue: 1.1 s
numericValue: 1143
estimated-input-latency:
id: estimated-input-latency
title: Estimated Input Latency
description: Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. [Learn more](https://web.dev/estimated-input-latency).
score: 1
scoreDisplayMode: numeric
displayValue: 10 ms
numericValue: 12.8
layout-shift-elements:
id: layout-shift-elements
title: Avoid large layout shifts
description: These DOM elements contribute most to the CLS of the page.
score:
scoreDisplayMode: informative
displayValue: 5 elements found
type: table
layout_shift_elements_headings: key: node itemType: node text: Element
node type: node node selector: div.row > div.col-12 > div.heading > h3.heading__sub node nodeLabel: Select a tool from the below to begin your site test
uses-webp-images:
id: uses-webp-images
title: Serve images in next-gen formats
description: Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images).
score: 1
scoreDisplayMode: numeric
displayValue:
resource-summary:
id: resource-summary
title: Keep request counts low and transfer sizes small
description: To set budgets for the quantity and size of page resources, add a budget.json file. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
score:
scoreDisplayMode: informative
displayValue: 27 requests • 682 KB
type: table
resource_summary_headings: key: label itemType: text text: Resource Type
server-response-time:
id: server-response-time
title: Initial server response time was short
description: Keep the server response time for the main document short because all other requests depend on it. [Learn more](https://web.dev/time-to-first-byte).
score: 1
scoreDisplayMode: binary
displayValue: Root document took 190 ms
numericValue: 190.146
type: opportunity
overallSavingsMs: -409.854
first-cpu-idle:
id: first-cpu-idle
title: First CPU Idle
description: First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
score: 1
scoreDisplayMode: numeric
displayValue: 1.1 s
numericValue: 1105
font-display:
id: font-display
title: Ensure text remains visible during webfont load
description: Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. [Learn more](https://web.dev/font-display).
score: 0
scoreDisplayMode: binary
type: table
efficient-animated-content:
id: efficient-animated-content
title: Use video formats for animated content
description: Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. [Learn more](https://web.dev/efficient-animated-content)
score: 1
scoreDisplayMode: numeric
numericValue: 0
type: opportunity
overallSavingsBytes: 0
overallSavingsMs: 0
total-blocking-time:
id: total-blocking-time
title: Total Blocking Time
description: Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more](https://web.dev/lighthouse-total-blocking-time).
score: 1
scoreDisplayMode: numeric
displayValue: 10 ms
numericValue: 13
uses-text-compression:
id: uses-text-compression
title: Enable text compression
description: Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. [Learn more](https://web.dev/uses-text-compression).
score: 1
scoreDisplayMode: numeric
numericValue: 0
total-byte-weight:
id: total-byte-weight
title: Avoids enormous network payloads
description: Large network payloads cost users real money and are highly correlated with long load times. [Learn more](https://web.dev/total-byte-weight).
score: 1
scoreDisplayMode: numeric
displayValue: Total size was 682 KB
numericValue: 698576
performance-budget:
id: performance-budget
title: Performance budget
description: Keep the quantity and size of network requests under the targets set by the provided performance budget. [Learn more](https://developers.google.com/web/tools/lighthouse/audits/budgets).
score:
scoreDisplayMode: notApplicable
largest-contentful-paint-element:
id: largest-contentful-paint-element
title: Largest Contentful Paint element
description: This is the element that was identified as the Largest Contentful Paint. [Learn More](https://web.dev/lighthouse-largest-contentful-paint)
score:
scoreDisplayMode: informative
displayValue: 1 element found
type: table
largest_contentful_paint_element_headings: key: node itemType: node text: Element
dom-size:
id: dom-size
title: Avoids an excessive DOM size
description: A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). [Learn more](https://web.dev/dom-size).
score: 0.99
scoreDisplayMode: numeric
displayValue: 556 elements
numericValue: 556
type: table
dom_size_headings: key: statistic itemType: text text: Statistic
dom_size_headings: key: element itemType: code text: Element
dom_size_headings: key: value itemType: numeric text: Value
dom_size_items: value: 556 statistic: Total DOM Elements
dom_size_items: value: 15 statistic: Maximum DOM Depth element value: element type: code
dom_size_items: value: 37 statistic: Maximum Child Elements element value:
element type: code
redirects:
id: redirects
title: Avoid multiple page redirects
description: Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects).
score: 1
scoreDisplayMode: numeric
numericValue: 0
type: opportunity
overallSavingsMs: 0
uses-rel-preload:
id: uses-rel-preload
title: Preload key requests
description: Consider using `` to prioritize fetching resources that are currently requested later in page load. [Learn more](https://web.dev/uses-rel-preload).
score: 1
scoreDisplayMode: numeric
numericValue: 0
type: opportunity
overallSavingsMs: 0
categoryGroups:
a11y-language title: Internationalization and localization
a11y-language description: These are opportunities to improve the interpretation of your content by users in different locales.
metrics title: Metrics
pwa-fast-reliable title: Fast and reliable
a11y-navigation title: Navigation
a11y-navigation description: These are opportunities to improve keyboard navigation in your application.
a11y-names-labels title: Names and labels
a11y-names-labels description: These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
diagnostics title: Diagnostics
diagnostics description: More information about the performance of your application. These numbers don't [directly affect](https://web.dev/performance-scoring/) the Performance score.
seo-content title: Content Best Practices
seo-content description: Format your HTML in a way that enables crawlers to better understand your app’s content.
a11y-aria title: ARIA
a11y-aria description: These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
best-practices-ux title: User Experience
seo-mobile title: Mobile Friendly
seo-mobile description: Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
seo-crawl title: Crawling and Indexing
seo-crawl description: To appear in search results, crawlers need access to your app.
budgets title: Budgets
budgets description: Performance budgets set standards for the performance of your site.
pwa-installable title: Installable
a11y-audio-video title: Audio and video
a11y-audio-video description: These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
a11y-tables-lists title: Tables and lists
a11y-tables-lists description: These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
a11y-best-practices title: Best practices
a11y-best-practices description: These items highlight common accessibility best practices.
best-practices-general title: General
best-practices-trust-safety title: Trust and Safety
pwa-optimized title: PWA Optimized
a11y-color-contrast title: Contrast
a11y-color-contrast description: These are opportunities to improve the legibility of your content.
load-opportunities title: Opportunities
load-opportunities description: These suggestions can help your page load faster. They don't [directly affect](https://web.dev/performance-scoring/) the Performance score.
best-practices-browser-compat: Browser Compatibility
timing total: 5846.83
varianceDisclaimer: Values are estimated and may vary. The [performance score is calculated](https://web.dev/performance-scoring/) directly from these metrics.
opportunityResourceColumnLabel: Opportunity
opportunitySavingsColumnLabel: Estimated Savings
errorMissingAuditInfo: Report error: no audit information
errorLabel: Error!
warningHeader: Warnings:
auditGroupExpandTooltip: Show audits
passedAuditsGroupTitle: Passed audits
notApplicableAuditsGroupTitle: Not applicable
manualAuditsGroupTitle: Additional items to manually check
toplevelWarningsMessage: There were issues affecting this run of Lighthouse:
crcLongestDurationLabel: Maximum critical path latency:
crcInitialNavigation: Initial Navigation
lsPerformanceCategoryDescription: [Lighthouse](https://developers.google.com/web/tools/lighthouse/) analysis of the current page on an emulated mobile network. Values are estimated and may vary.
labDataTitle: Lab Data
Page Title : Geekflare Tools for Security, Performance, DNS, IP, Hosting and SEO
You have a page title but it\'s too long and exceeds 70 characters. You should shorten your page title.
About this SEO factor:
A page title is often treated as the most important on-page element. It is a strong relevancy signal for search engines because it tells them what the page is really about. It is of course important that title includes your most important keywords. More than that, every page should have a unique title to ensure that search engines have no trouble in determining which of the website pages is relevant for each query. Pages with a duplicate title have less chance of ranking high and the other pages may be hard to get ranked as well.
If a page doesn't have a title, or the title tag is empty (i.e. it just looks like this in the code: <title></title>), Google and other search engines will decide on their own, what content to show on the results page. Therefore, if the page ranks on Google for a keyword and someone sees it in the results for their search, they may not click on it because it is not clear. Every time you are creating a webpage, don't forget to add a meaningful title that will attract your audience.
Meta Description : Geekflare Toolbox - More than 15 FREE tools to test your website security, performance, domain health, and search engine ranking factors
Your meta description does not exceed 150 characters. It's fine.
About this SEO factor:
Description is the full interpretation of your website content and features. Most often it is a short paragraph that describe what are features and information provided by the website to its visitors. You may consider it a advertising of your website. Although not important for search engine ranking but very important for hits or visits through search engine results. Description should be less than 150 character because search engine shows this length of paragraph on search result. And every page of website should contain an unique description to avoid description duplication. Description is the definition of your website for user experience so form it as complete but short and precise illustration of your website.
Meta keywords are keywords inside Meta tags. Meta keywords are not likely to be used for search engine ranking. the words of title and description can be used as meta keywords. it is a good idea for SEO other than search engine ranking.
The most using keywords do not match with meta keywords.
About this SEO factor:
Keyword usage is the using of your keywords inside Meta tags and contents of your website. Use keywords that describes your site properly for precise search engine result of your website.
Unique words are uncommon words that reflects your site features and informations. Search engine metrics are not intended to use unique words as ranking factor but it is still useful to get a proper picture of your site contents. Using positive unique words like complete, perfect, shiny, is a good idea user experience.
Stop words are common words like all the preposition, some generic words like download, click me, offer, win etc. since most used keyword may be a slight factor for visitors you are encouraged to use more unique words and less stop words.
The ideal page's ratio of text to HTML code must be lie between 20 to 60%.
Because if it is come less than 20% it means you need to write more text in your web page while in case of more than 60% your page might be considered as spam.
Select a tool from the below to begin your site test
H4(39)
HTTP Headers Checker
Secure Headers Test
HSTS Test
HPKP Test
X-Frame-Options Test
X-XSS-Protection Test
MIME Sniffing Test
CSP Test
Cross-Domain-Policy Test
Referrer-Policy Test
Expect-CT Test
Feature-Policy Test
Secure Cookie Test
Server Signature Test
DNS Record Lookup
SPF Record Lookup
IPv6 Test
CAA Record Lookup
Ping Test
Traceroute Test
TLS 1.3 Test
TLS Scanner
DNSSEC Test
HTTP/2 Test
HTTP/3 Test
TCP Port Scanner
IP Location
Whois Hosting
What’s My IP
Blacklist Lookup
TTFB Test
Website Performance Audit
WordPress Security Scanner
Broken Link Checker
Mixed Content Checker
Capture Screenshot
Sprint Name Generator
Navigation
Popular Tools
H5(1)
Share
H6(0)
About this SEO factor:
h1 status is the existence of any content inside h1 tag. Although not important like Meta titles and descriptions for search engine ranking but still a good way to describe your contents in search engine result.
h2 status less important but should be used for proper understanding of your website for visitor.
robots.txt is text file that reside on website root directory and contains the instruction for various robots (mainly search engine robots) for how to crawl and indexing your website for their webpage. robots.txt contains the search bots or others bots name, directory list allowed or disallowed to be indexing and crawling for bots, time delay for bots to crawl and indexing and even the sitemap url. A full access or a full restriction or customized access or restriction can be imposed through robots.txt.
robots.txt is very important for SEO. Your website directories will be crawled and indexed on search engine according to robots.txt instructions. So add a robots.txt file in your website root directory. Write it properly including your content enriched pages and other public pages and exclude any pages which contain sensitive information. Remember robots.txt instruction to restrict access to your sensitive information of your page is not formidable on web page security ground. So do not use it on security purpose.
Learn more
Sitemap is a xml file which contain full list of your website urls. It is used to include directories of your websites for crawling and indexing for search engine and access for users. it can help search engine robots for indexing your website more fast and deeply. It is roughly an opposite of robots.txt
You can create a sitemap.xml by various free and paid service or you can write it with proper way (read about how write a sitemap).
Also keep these things in mind:
1) Sitemap must be less than 10 MB (10,485,760 bytes) and can contain maximum 50,000 urls. if you have more uls than this create multiple sitemap files and use a sitemap index file.
2) Put your sitemap in website root directory and add the url of your sitemap in robots.txt.
3) sitemap.xml can be compressed using grip for faster loading.
Broken link: a broken link is an inaccessible link or url of a website. a higher rate of broken links have a negative effect on search engine ranking due to reduced link equity. it also has a bad impact on user experience. There are several reasons for broken link. All are listed below.
1) An incorrect link entered by you.
2) The destination website removed the linked web page given by you. (A common 404 error).
3) The destination website is irreversibly moved or not exists anymore. (Changing domain or site blocked or dysfunctional).
4) User may behind some firewall or alike software or security mechanism that is blocking the access to the destination website.
5) You have provided a link to a site that is blocked by firewall or alike software for outside access. Learn more or Learn more
NoIndex : noindex directive is a meta tag value. noindex directive is for not to show your website on search engine results. You must not set ‘noindex’ as value in meta tags if you want to be your website on search engine result.
By default, a webpage is set to “index.” You should add a <meta name="robots" content="noindex" /> directive to a webpage in the <head> section of the HTML if you do not want search engines to crawl a given page and include it in the SERPs (Search Engine Results Pages).
DoFollow & NoFollow : nofollow directive is a meta tag value. Nofollow directive is for not to follow any links of your website by search engine bots. You must not set ‘nofollow’ as value in meta tags if you want follow your link by search engine bots.
By default, links are set to “follow.” You would set a link to “nofollow” in this way: <a href="http://www.example.com/" rel="nofollow">Anchor Text</a> if you want to suggest to Google that the hyperlink should not pass any link equity/SEO value to the link target.
An SEO friendly link is roughly follows these rules. The url should contain dash as a separator, not to contain parameters and numbers and should be static urls.
To resolve this use these techniques.
1) Replace underscore or other separator by dash, clean url by deleting or replaceing number and parameters.
2) Marge your www and non www urls.
3) Do not use dynamic and related urls. Create an xml sitemap for proper indexing of search engine.
4) Block unfriendly and irrelevant links through robots.txt.
5) Endorse your canonical urls in canonical tag. Learn more
An alternate title for image. Alt attribute content to describe an image. It is necessary for notifying search engine spider and improve actability to your website. So put a suitable title for your image at least those are your website content not including the images for designing your website. To resolve this put a suitable title in your alt attributes. Learn more
Older HTML tags and attributes that have been superseded by other more functional or flexible alternatives (whether as HTML or as CSS ) are declared as deprecated in HTML4 by the W3C - the consortium that sets the HTML standards. Browsers should continue to support deprecated tags and attributes, but eventually these tags are likely to become obsolete and so future support cannot be guaranteed.
HTML page size is the one of the main factors of webpage loading time. It should be less than 100 KB according to google recommendation. Note that, this size not including external css, js or images files. So small page size less loading time.
To reduce your page size do this steps
1) Move all your css and js code to external file.
2) make sure your text content be on top of the page so that it can displayed before full page loading.
3) Reduce or compress all the image, flash media file etc. will be better if these files are less than 100 KB Learn more
GZIP is a generic compressor that can be applied to any stream of bytes: under the hood it remembers some of the previously seen content and attempts to find and replace duplicate data fragments in an efficient way - for the curious, great low-level explanation of GZIP. However, in practice, GZIP performs best on text-based content, often achieving compression rates of as high as 70-90% for larger files, whereas running GZIP on assets that are already compressed via alternative algorithms (e.g. most image formats) yields little to no improvement. It is also recommended that, GZIP compressed size should be <=33 KB
Inline css is the css code reside in html page under html tags not in external .css file. Inline css increases the loading time of your webpage which is an important search engine ranking factor. So try not to use inline css.
Internal css is the css codes which resides on html page inside style tag. Internal css is increases loading time since no page caching is possible for internal css. Try to put your css code in external file.
Micro data is the information underlying a html string or paragraph. Consider a string “Avatar”, it could refer a profile picture on forum, blog or social networking site or may it refer to a highly successful 3D movie. Microdot is used to specify the reference or underlying information about an html string. Microdata gives chances to search engine and other application for better understanding of your content and better display significantly on search result.
Learn more
If multiple domain name is registered under single ip address the search bots can label other sites as duplicates of one sites. This is ip canonicalization. Little bit like url canonicalizaion. To solve this use redirects.
Learn more
Canonical tags make your all urls those lead to a single address or webpage into a single url. Like : <link rel="canonical" href="https://mywebsite.com/home" /> <link rel="canonical" href="https://www.mywebsite.com/home" />
Both refer to the link mywebsite.com/home. So all the different url with same content or page now comes under the link or url mywebsite.com/home. Which will boost up your search engine ranking by eliminating content duplication.
Use canonical tag for all the same urls. Learn more
Site passed plain text email test. No plain text email found.
About this SEO factor:
Plain text email address is vulnerable to email scrapping agents. An email scrapping agent crawls your website and collects every Email address which written in plain text. So existence of plain text email address in your website can help spammers in email Harvesting. This could be a bad sign for search engine.
To fight this you can obfuscate your email addresses in several ways:
1) CSS pseudo classes.
2) Writing backward your email address.
3) Turn of display using css.
4) Obfuscate your email address using javascript.
5) Using wordpress and php (wordpress site only). Learn more
Your page does not appear to have any app install interstitials that hide a significant amount of content. Learn more about the importance of avoiding the use of app install interstitials.
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Images are often the largest part of a page and account for most of the downloaded data. As a result, optimizing images can often be the largest savings and performance improvement. The less data the browser has to download the faster the page will load.
Optimizing image works by removing unnecessary data that is saved in the images. This can reduce the total page load size by up to 80%.
Your above-the-fold content is properly prioritized.
About this SEO factor:
Visible content is the portion of a webpage users see on their screen before they scroll. It is sometimes referred to as "above the fold" content. Websites that seem very fast and crisp to load are often just as large as slow websites, they have just prioritized the visible content so the site appears to load faster. Google prefers webpages that show content quickly.
Google suggests two main strategies for prioritizing the visible content. First, structure your HTML to load the critical content first, such as the main contents instead of ads or navigation. Next, reduce the amount of data used by your resources by using techniques such as image optimization, minification, and by removing unnecessary elements.