SeoReviewer | breakfastburn-usa.us/

Health report : https://www.breakfastburn-usa.us/

Follow recommendations of this health report to keep your site healthy

Examined at : 2023-03-16 05:59:55

SeoReviewer found 11 major issues

Score

page title

page title : Breakfast Burn™ (Official) | Get Over 80% off Today Only!

Your page title does not exceed 60 characters. It's fine.

Knowledge Base

Title is the heading of the webpage. The sentence or string enclosed between html title tag () is the title of your website. Search engines searches for the title of your website and displays title along with your website address on search result. Title is the most important element for both SEO and social sharing. Title should be less than 50 to 60 characters because search engine typically displays this length of string or sentence on search result. A good title can consist the primary keyword, secondary keyword and brand name. For example a fictitious gaming information providing sites title may be like "the future of gaming information is here". A webpage title should contain a proper glimpse of the website. title is important element as an identification of your website for user experience, SEO and social sharing. So have a nice and catching title.
Learn more

Meta Description

Meta Description : Get Breakfast Burn Supplement With Discount. Order Now On The Official Website With Free Shipping. 100% Safe & Secure, FDA Approved

Your meta description does not exceed 150 characters. It's fine.

Knowledge Base

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 Keyword

Meta Keyword : BreakfastBurn, Breakfast Burn, BreakfastBurn supplement, BreakfastBurn buy, buy BreakfastBurn

Knowledge Base

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.

Single Keywords

Keyword	Occurrence	Density	Possible Spam
Breakfast	44	2.688 %	No
Burn	39	2.382 %	No
USA	11	0.672 %	No
made	8	0.489 %	No
shipping	8	0.489 %	No
body	7	0.428 %	No
helps	7	0.428 %	No
weight	7	0.428 %	No
fat	7	0.428 %	No
Save	7	0.428 %	No
FREE	6	0.367 %	Yes
blood	6	0.367 %	No
natural	6	0.367 %	No
supplement	6	0.367 %	No
levels	6	0.367 %	No
tinnitus	6	0.367 %	No
Total	6	0.367 %	No
Month	6	0.367 %	No
Bottle	6	0.367 %	No
health	6	0.367 %	No

Two Word Keywords

Keyword	Occurrence	Density	Possible Spam
Breakfast Burn	39	2.382 %	No
Burn is	10	0.611 %	No
in the	9	0.55 %	No
FREE shipping	6	0.367 %	No
the USA	6	0.367 %	No
Month Supply	6	0.367 %	No
Bottle Total	6	0.367 %	No
You Save	6	0.367 %	No
Per Bottle	6	0.367 %	No
is 100	5	0.305 %	No
is made	5	0.305 %	No
Burn Supplement	4	0.244 %	No
made in	4	0.244 %	No
blood sugar	4	0.244 %	No
You can	4	0.244 %	No
way to	3	0.183 %	No
I had	3	0.183 %	No
is a	3	0.183 %	No
of Breakfast	3	0.183 %	No
losing weight	3	0.183 %	No

Three Word Keywords

Keyword	Occurrence	Density	Possible Spam
Breakfast Burn is	10	0.611 %	No
Per Bottle Total	6	0.367 %	No
in the USA	5	0.305 %	No
is made in	4	0.244 %	No
Breakfast Burn Supplement	4	0.244 %	No
Burn is 100	3	0.183 %	No
made in the	3	0.183 %	No
is 100 natural	2	0.122 %	No
100 natural made	2	0.122 %	No
natural made with	2	0.122 %	No
made with only	2	0.122 %	No
with only the	2	0.122 %	No
only the highest	2	0.122 %	No
the highest quality	2	0.122 %	No
highest quality ingredients	2	0.122 %	No
Burn is made	2	0.122 %	No
for many years	2	0.122 %	No
seems to be	2	0.122 %	No
100 All Natural	2	0.122 %	No
is 100 gmp	2	0.122 %	No

Four Word Keywords

Keyword	Occurrence	Density	Possible Spam
is made in the	3	0.183 %	No
made in the USA	3	0.183 %	No
Breakfast Burn is 100	3	0.183 %	No
Made In The USA	2	0.122 %	No
411 117 You Save	2	0.122 %	No
to the latest standards	2	0.122 %	No
Only for 34per bottle	2	0.122 %	No
bottle Only for 34per	2	0.122 %	No
USA Verified Purchase I	2	0.122 %	No
Verified Purchase I had	2	0.122 %	No
Breakfast Burn Supplement is	2	0.122 %	No
Save 294 FREE shipping	2	0.122 %	No
You Save 294 FREE	2	0.122 %	No
117 You Save 294	2	0.122 %	No
Bottle Total 411 117	2	0.122 %	No
Total 411 117 You	2	0.122 %	No
manufactured according to the	2	0.122 %	No
Per Bottle Total 411	2	0.122 %	No
39 Per Bottle Total	2	0.122 %	No
Supply 39 Per Bottle	2	0.122 %	No

Keyword Usage

The most using keywords match with meta keywords.

Knowledge Base

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.

Total Words

Total Words : 1637

Knowledge Base

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.

Text/HTML Ratio Test

Site failed text/HTML ratio test.

Text/HTML Ratio Test : 3%

Knowledge Base

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.

HTML Headings

H1(1)

Breakfast Burn™ Only $34/Bottle Today- Grab Before The Offer Expires!

H2(10)

Today! - Special Offer Save Over 80%!
Why should you choose Breakfast Burn™?
What is Breakfast Burn ?
How Does Breakfast Burn™ Works?
Limited Time Special Pricing - Act Now!
Key Ingredients Of Breakfast Burn
180-DAYS 100% MONEY-BACK GUARANTEE
Proven By Thousands
Limited time special pricing - shipping and handling free!
Breakfast Burn Supplement Frequently Asked Questions

H3(0)

H4(0)

H5(0)

H6(0)

Knowledge Base

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.

Robot.txt

Your site have robot.txt

Robot.txt

> User-agent: *

Knowledge Base

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

Your site does not have sitemap

Knowledge Base

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

Internal Vs. External Links

Total Internal Links? 3

Total External Links? 9

Internal Links

https://www.breakfastburn-usa.us/ed334ed3-f5655e13-f218d1f9
https://www.breakfastburn-usa.us/f8251b31-de4ca09d-5463dbfd
https://www.breakfastburn-usa.us/b5008add-54249fd7-8f1d864d

External Links

https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://96832ysv0ta9gyq3-7ggq37lkr.hop.clickbank.net
https://systeme.io/?sa=sa0041222723fb49744fc19f2c1ce10d2ba484b42e

Alexa Rank

Traffic Rank

A PHP Error was encountered

Severity: Notice

Message: Trying to access array offset on value of type null

Filename: site/report.php

Line Number: 936

Reach Rank

A PHP Error was encountered

Severity: Notice

Message: Trying to access array offset on value of type null

Filename: site/report.php

Line Number: 946

Top Country

A PHP Error was encountered

Severity: Notice

Message: Trying to access array offset on value of type null

Filename: site/report.php

Line Number: 956

Top Country Rank

A PHP Error was encountered

Severity: Notice

Message: Trying to access array offset on value of type null

Filename: site/report.php

Line Number: 966

Domain IP Information

ISP

Organization

City

Country

Time Zone

Longitude

Latitude

NoIndex , NoFollow, DoDollow Links

Total NoIndex Links 0

Total NoFollow Links 0

Total DoFollow Links 12

NoIndex Enabled By Meta Robot? No

NoFollow Enabled By Meta Robot? No

NoIndex Links

NoFollow Links

Knowledge Base

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.

Learn more

SEO Friendly Links

Links of your site are SEO friendly.

Knowledge Base

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

Favicon

Your site have favicon.

Learn more

Image 'alt' Test

Your site does not have any image without alt text.

Knowledge Base

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

DOC Type

DOC Type : <!DOCTYPE html>

Page have doc type.

Knowledge Base

doc type is not SEO factor but it is checked for validating your web page. So set a doctype at your html page.
Learn more

Depreciated HTML Tag

Your site does not have any depreciated HTML tag.

Knowledge Base

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

HTML Page Size : 472 KB

HTML page size is > 100KB

Knowledge Base

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 Compression

GZIP compression is disabled.

Knowledge Base

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

Your site have 124 inline css.

Inline CSS

<a href="https://www.breakfastburn-usa.us/ed334ed3-f5655e13-f218d1f9" style=""></a>
<a href="https://www.breakfastburn-usa.us/f8251b31-de4ca09d-5463dbfd" style=""></a>
<a href="https://www.breakfastburn-usa.us/b5008add-54249fd7-8f1d864d" style=""></a>

Knowledge Base

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.

A PHP Error was encountered

Severity: Warning

Message: count(): Parameter must be an array or an object that implements Countable

Filename: site/report.php

Line Number: 1680

Internal CSS

Your site does not have any internal css.

Knowledge Base

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 Schema Test

Site failed micro data schema test.

Knowledge Base

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

IP & DNS Report

IPv4 18.64.155.61

IPv6 2600:9000:2343:5000:f:e0e7:8780:93a1

DNS Report

SL	Host	Class	TTL	Type	PRI	Target	IP
1	dzfqrzzywnk7y.cloudfront.net	IN	58	A			18.64.155.127
2	dzfqrzzywnk7y.cloudfront.net	IN	58	A			18.64.155.48
3	dzfqrzzywnk7y.cloudfront.net	IN	58	A			18.64.155.50
4	dzfqrzzywnk7y.cloudfront.net	IN	58	A			18.64.155.61
5	dzfqrzzywnk7y.cloudfront.net	IN	21600	NS		ns-1128.awsdns-13.org
6	dzfqrzzywnk7y.cloudfront.net	IN	21600	NS		ns-788.awsdns-34.net
7	dzfqrzzywnk7y.cloudfront.net	IN	21600	NS		ns-1775.awsdns-29.co.uk
8	dzfqrzzywnk7y.cloudfront.net	IN	21600	NS		ns-414.awsdns-51.com
9	www.breakfastburn-usa.us	IN	1626	CNAME		dzfqrzzywnk7y.cloudfront.net
10	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:8e00:f:e0e7:8780:93a1
11	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:7c00:f:e0e7:8780:93a1
12	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:1600:f:e0e7:8780:93a1
13	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:c000:f:e0e7:8780:93a1
14	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:d600:f:e0e7:8780:93a1
15	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:7800:f:e0e7:8780:93a1
16	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:9a00:f:e0e7:8780:93a1
17	dzfqrzzywnk7y.cloudfront.net	IN	58	AAAA			2600:9000:2343:5000:f:e0e7:8780:93a1

IP Canonicalization Test

Site failed IP canonicalization test.

Knowledge Base

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

URL Canonicalization Test

Site passed URL canonicalization test.

Knowledge Base

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

Plain Text Email Test

Site passed plain text email test. No plain text email found.

Knowledge Base

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

CURL Response

url	https://www.breakfastburn-usa.us/	content type	text/html; charset=UTF-8
http code	200	header size	725
request size	151	filetime	-1
ssl verify result	20	redirect count	0
total time	0.716666	namelookup time	0.032307
connect time	0.038467	pretransfer time	0.05013
size upload	0	size download	483554
speed download	674727	speed upload	0
download content length	-1	upload content length	0
starttransfer time	0.303224	redirect time	0
redirect url		primary ip	2600:9000:2343:8e00:f:e0e7:8780:93a1
certinfo		primary port	443
local ip	2a02:4780:1:19::10	local port	30610
http version	3	protocol	2
ssl verifyresult	0	scheme	HTTPS
appconnect time us	50054	connect time us	38467
namelookup time us	32307	pretransfer time us	50130
redirect time us	0	starttransfer time us	303224
total time us	716666

PageSpeed Insights (Mobile)

Performance

Emulated Form Factor Mobile

Locale En-US

Category Performance

Field Data

First Contentful Paint (FCP)

FCP Metric Category

First Input Delay (FID)

FID Metric Category

Overall Category

Origin Summary

First Contentful Paint (FCP)

FCP Metric Category

First Input Delay (FID)

FID Metric Category

Overall Category

Lab Data

First Contentful Paint 5.0 s

First Meaningful Paint 5.0 s

Speed Index 5.1 s

First CPU Idle

Time To Interactive 17.1 s

Max Potential First Input Delay 2,670 ms

Audit Data

Keep request counts low and transfer sizes small


												                		37 requests • 2,271 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn More

Eliminate render-blocking resources


												                		Potential savings of 1,780 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn More

Enable text compression


												                		Potential savings of 404 KiB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More

Serve static assets with an efficient cache policy


												                		3 resources found

A long cache lifetime can speed up repeat visits to your page. Learn More

Reduce the impact of third-party code


												                		Third-party code blocked the main thread for 2,720 ms

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

First Contentful Paint (3G)


												                		10890 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn More

Total Blocking Time


												                		2,540 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time


												                		3.3 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More

Server Backend Latencies


												                		0 ms

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

Properly size images


												                		Potential savings of 307 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn More

Reduce unused CSS


												                		Potential savings of 99 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More

Avoids enormous network payloads


												                		Total size was 2,271 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn More

Minimize main-thread work


												                		5.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More

Avoid chaining critical requests


												                		10 chains found

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

Avoid an excessive DOM size


												                		1,224 elements

A large DOM will increase memory usage, cause longer Learn More

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn More

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn More

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More

Network Round Trip Times


												                		0 ms

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

PageSpeed Insights (Desktop)

Performance

Emulated Form Factor Desktop

Locale En-US

Category Performance

Field Data

First Contentful Paint (FCP)

FCP Metric Category

First Input Delay (FID)

FID Metric Category

Overall Category

Origin Summary

First Contentful Paint (FCP)

FCP Metric Category

First Input Delay (FID)

FID Metric Category

Overall Category

Lab Data

First Contentful Paint 1.2 s

First Meaningful Paint 1.5 s

Speed Index 1.2 s

First CPU Idle

Time To Interactive 3.8 s

Max Potential First Input Delay 660 ms

Audit Data

Keep request counts low and transfer sizes small


												                		41 requests • 2,431 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn More

Eliminate render-blocking resources


												                		Potential savings of 520 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn More

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn More

Enable text compression


												                		Potential savings of 404 KiB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn More

Serve static assets with an efficient cache policy


												                		3 resources found

A long cache lifetime can speed up repeat visits to your page. Learn More

Reduce the impact of third-party code


												                		Third-party code blocked the main thread for 600 ms

Total Blocking Time


												                		630 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time


												                		0.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn More

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn More

Server Backend Latencies


												                		0 ms

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

Properly size images


												                		Potential savings of 476 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn More

Reduce unused CSS


												                		Potential savings of 109 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn More

Avoids enormous network payloads


												                		Total size was 2,431 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn More

Minimizes main-thread work


												                		1.2 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn More

Avoid chaining critical requests


												                		11 chains found

Avoid an excessive DOM size


												                		1,224 elements

A large DOM will increase memory usage, cause longer Learn More

Avoid multiple page redirects

Redirects introduce additional delays before the page can be loaded. Learn More

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn More

User Timing marks and measures

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn More

Network Round Trip Times


												                		0 ms

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