Powered by https://doc.4-seo.de ()

health report : https://fellfein-berlin.de

examined at : 25-08-04 10:55:16

follow recommendations of this health report to keep your site healthy

profile card
https://fellfein-berlin.de
Website Health Report powered by https://doc.4-seo.de
  Aug 4, 2025 10:55:16
22.2 / 100
Overall Score
79.67 / 100
Desktop Score
56.54 / 100
Mobile Score

Compare
Download Pdf
Please provide your information, a download link will be sent to you

Page Title

Page Title

Start - Tiersalon fellfein

Short Recommendation

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

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

Herzlich Willkommen Tiersalon fellfein - Ihr Tiersalon in Berlin Lichtenberg!Hier stehen die Pflege und das Wohlbefinden Ihres Haustiers im Mittelpunkt. Als ausgebildete Hundefriseurin mit medizinischem Fachwissen bin ich für Sie und ihren tierischen Freund da. Liebevoll und professionell - für jedes Fell die richtige Pflege. Kontakt Erfahren Sie mehr

Short Recommendation

Your meta description exceeds 150 characters. It's not good.

description_recommendation

Meta Keyword

Meta Keyword

Short Recommendation

Your site do not have any meta keyword.

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.

Keyword Analysis

Single Keywords

Keyword Occurrence Density Possible Spam
Tiersalon 3 4.918 % No
und 3 4.918 % No
die 2 3.279 % No
Kontakt 2 3.279 % No
für 2 3.279 % No
Sie 2 3.279 % No
fellfein 2 3.279 % No
– 2 3.279 % No
Pflege 2 3.279 % No
Tel 1 1.639 % No
Fachwissen 1 1.639 % No
bin 1 1.639 % No
ich 1 1.639 % No
ihren 1 1.639 % No
tierischen 1 1.639 % No
Liebevoll 1 1.639 % No
Freund 1 1.639 % No
da 1 1.639 % No
mit 1 1.639 % No
professionell 1 1.639 % No

Two Word Keywords

Keyword Occurrence Density Possible Spam
Tiersalon fellfein 2 3.279 % No
Tel 0163 1 1.639 % No
Liebevoll und 1 1.639 % No
mit medizinischem 1 1.639 % No
medizinischem Fachwissen 1 1.639 % No
Fachwissen bin 1 1.639 % No
bin ich 1 1.639 % No
ich für 1 1.639 % No
für Sie 1 1.639 % No
Sie und 1 1.639 % No
und ihren 1 1.639 % No
ihren tierischen 1 1.639 % No
tierischen Freund 1 1.639 % No
Freund da 1 1.639 % No
da Liebevoll 1 1.639 % No
professionell – 1 1.639 % No
und professionell 1 1.639 % No
ausgebildete Hundefriseurin 1 1.639 % No
– für 1 1.639 % No
für jedes 1 1.639 % No

Three Word Keywords

Keyword Occurrence Density Possible Spam
Tel 0163 25 1 1.639 % No
und professionell – 1 1.639 % No
mit medizinischem Fachwissen 1 1.639 % No
medizinischem Fachwissen bin 1 1.639 % No
Fachwissen bin ich 1 1.639 % No
bin ich für 1 1.639 % No
ich für Sie 1 1.639 % No
für Sie und 1 1.639 % No
Sie und ihren 1 1.639 % No
und ihren tierischen 1 1.639 % No
ihren tierischen Freund 1 1.639 % No
tierischen Freund da 1 1.639 % No
Freund da Liebevoll 1 1.639 % No
da Liebevoll und 1 1.639 % No
Liebevoll und professionell 1 1.639 % No
professionell – für 1 1.639 % No
ausgebildete Hundefriseurin mit 1 1.639 % No
– für jedes 1 1.639 % No
für jedes Fell 1 1.639 % No
jedes Fell die 1 1.639 % No

Four Word Keywords

Keyword Occurrence Density Possible Spam
Tel 0163 25 60 1 1.639 % No
und professionell – für 1 1.639 % No
mit medizinischem Fachwissen bin 1 1.639 % No
medizinischem Fachwissen bin ich 1 1.639 % No
Fachwissen bin ich für 1 1.639 % No
bin ich für Sie 1 1.639 % No
ich für Sie und 1 1.639 % No
für Sie und ihren 1 1.639 % No
Sie und ihren tierischen 1 1.639 % No
und ihren tierischen Freund 1 1.639 % No
ihren tierischen Freund da 1 1.639 % No
tierischen Freund da Liebevoll 1 1.639 % No
Freund da Liebevoll und 1 1.639 % No
da Liebevoll und professionell 1 1.639 % No
Liebevoll und professionell – 1 1.639 % No
professionell – für jedes 1 1.639 % No
ausgebildete Hundefriseurin mit medizinischem 1 1.639 % No
– für jedes Fell 1 1.639 % No
für jedes Fell die 1 1.639 % No
jedes Fell die richtige 1 1.639 % No

Keyword Usage

Keyword Usage

Short Recommendation

The most using keywords do not match with meta keywords.

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.

Sitemap

Short Recommendation

Your site have sitemap

Location

https://fellfein-berlin.de/sitemap.xml

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

Total Words

Total Words

61

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 : 1%

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)
  • Tiersalon fellfein
  • H2(2)
  • Tel: 0163 25 60 941
  • Herzlich Willkommen
  • H3(0)
  • H4(0)
  • H5(0)
  • H6(0)

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

Short Recommendation

Your site have robot.txt

  • robot.txt
  • User-agent: * Disallow: /wp-admin/ Allow: /wp-admin/admin-ajax.php Sitemap: https://fellfein-berlin.de/sitemap.xml Sitemap: https://fellfein-berlin.de/sitemap.rss


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

Internal Vs. External Links

Total Internal Links?

10

Total External Links?

0
  • Internal Links
  • https://fellfein-berlin.de/
  • https://fellfein-berlin.de/ueber/
  • https://fellfein-berlin.de/?page_id=97
  • https://fellfein-berlin.de/kontakt/
  • https://fellfein-berlin.de/dienstleistungen/
  • /kontakt
  • https://fellfein-berlin.de/ueber/
  • https://fellfein-berlin.de
  • https://fellfein-berlin.de/impressum/
  • https://fellfein-berlin.de/268-2
  • External Links

Domain IP Information

IP

217.160.0.41

City

Duisburg

Country

DE

Time Zone

Europe/Berlin

Longitude

6.7652

Latitude

51.4325

NoIndex , NoFollow, DoFollow Links

Total NoIndex Links

0

Total NoFollow Links

0

Total DoFollow Links

10

NoIndex Enabled by Meta Robot?

No

NoFollow Enabled by Meta Robot?

No
  • NoIndex Links
  • NoFollow Links

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

Short Recommendation

Some links of your site are not SEO friendly.

  • Not SEO Friendly Links
  • https://fellfein-berlin.de/?page_id=97

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

Plain Text Email Test

Short Recommendation

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


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

Favicon

Short Recommendation

Your site have favicon.

DOC Type

DOC Type : <!DOCTYPE html>
Short Recommendation

Page have doc type.

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

Image 'alt' Test

Short Recommendation

Your site have 1 images without alt text.

  • Images Without alt
  • https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-1024x768.jpg

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

Depreciated HTML Tag

Short Recommendation

Your site does not have any depreciated HTML tag.


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 : 85 KB
Short Recommendation

HTML page size is <= 100KB

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

Short Recommendation

GZIP compression is disabled.

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

Short Recommendation

Your site have 13 inline css.

  • Inline CSS
  • <div class="wp-block-group alignfull has-background-color has-white-color has-black-background-color has-text-color has-background has-link-color wp-elements-98ac53698168d2fd3d67ced255939083 has-global-padding is-layout-constrained wp-container-core-group-is-layout-bc3c219d wp-block-group-is-layout-constrained" style="border-style:none;border-width:0px;border-radius:0px;margin-top:var(--wp--preset--spacing--20);margin-bottom:var(--wp--preset--spacing--20);padding-top:var(--wp--preset--spacing--20);padding-right:var(--wp--preset--spacing--40);padding-bottom:var(--wp--preset--spacing--20);padding-left:var(--wp--preset--spacing--40);background-image:url(&#039;https://fellfein-berlin.de/wp-content/uploads/2024/08/Screenshot-2024-08-29-154649.png&#039;);background-position:1% 16%;background-size:auto;"></div>
  • <h2 class="wp-block-heading has-text-align-center has-text-color has-link-color has-large-font-size wp-elements-326e066ec16d73e0cdf9d96e81640126 wp-container-content-f67f277b" style="color:#c22c71"></h2>
  • <main class="wp-block-group is-layout-flow wp-block-group-is-layout-flow" style="margin-top:0px;margin-bottom:0px"></main>
  • <div class="wp-block-cover alignfull is-light" style="padding-right:var(--wp--preset--spacing--70);padding-left:var(--wp--preset--spacing--70);min-height:106px;aspect-ratio:unset;"></div>
  • <span aria-hidden="true" class="wp-block-cover__background has-background-dim-40 has-background-dim" style="background-color:#dfdfdf"></span>
  • <h2 class="wp-block-heading has-text-align-right has-text-color has-link-color has-karla-font-family has-large-font-size wp-elements-5fa5008aa24ed07394eb999b85fff015" style="color:#c22c71"></h2>
  • <div class="wp-block-group alignfull has-background-background-color has-background is-vertical is-layout-flex wp-container-core-group-is-layout-c1828443 wp-block-group-is-layout-flex" style="margin-top:0;margin-bottom:0;padding-top:0;padding-right:0;padding-bottom:0;padding-left:0"></div>
  • <div class="wp-block-columns alignwide are-vertically-aligned-center is-layout-flex wp-container-core-columns-is-layout-968063f1 wp-block-columns-is-layout-flex" style="padding-right:var(--wp--preset--spacing--40);padding-left:var(--wp--preset--spacing--40)"></div>
  • <img decoding="async" width="1024" height="768" src="https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-1024x768.jpg" alt="" class="wp-image-44" style="aspect-ratio:1;object-fit:contain;width:498px;height:auto" srcset="https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-1024x768.jpg 1024w, https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-300x225.jpg 300w, https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-768x576.jpg 768w, https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-1536x1152.jpg 1536w, https://fellfein-berlin.de/wp-content/uploads/2024/08/IMG_20230320_183713-2048x1536.jpg 2048w" sizes="(max-width: 1024px) 100vw, 1024px" />
  • <p class="has-karla-font-family" style="margin-top:16px"></p>
  • <div class="wp-block-buttons is-layout-flex wp-container-core-buttons-is-layout-12dcd427 wp-block-buttons-is-layout-flex" style="margin-top:var(--wp--preset--spacing--40)"></div>
  • <a class="wp-block-button__link has-background wp-element-button" href="/kontakt" style="background-color:#c22c71"></a>
  • <div class="wp-block-group alignfull has-background-color has-global-padding is-layout-constrained wp-container-core-group-is-layout-5d2f8bdc wp-block-group-is-layout-constrained" style="margin-top:0;margin-bottom:0;padding-top:var(--wp--preset--spacing--40);padding-right:var(--wp--preset--spacing--30);padding-bottom:var(--wp--preset--spacing--40);padding-left:var(--wp--preset--spacing--30)"></div>

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

Short Recommendation

Your site have 22 internal 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 Schema Test

Short Recommendation

Site failed micro data schema test.

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

217.160.0.41

IPv6

2001:8d8:100f:f000::200
DNS Report
SL Host Class TTL Type PRI Target IP
1fellfein-berlin.deIN3575A217.160.0.41
2fellfein-berlin.deIN3600NSns1067.ui-dns.biz
3fellfein-berlin.deIN3600NSns1065.ui-dns.de
4fellfein-berlin.deIN3600NSns1037.ui-dns.com
5fellfein-berlin.deIN3600NSns1120.ui-dns.org
6fellfein-berlin.deIN3600MX10mx01.ionos.de
7fellfein-berlin.deIN3600MX10mx00.ionos.de
8fellfein-berlin.deIN3576AAAA2001:8d8:100f:f000::200

IP Canonicalization Test

Short Recommendation

Site failed IP canonicalization test.

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

Short Recommendation

Site passed URL canonicalization test.

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

cURL Response

  • url : https://fellfein-berlin.de/
  • content type : text/html; charset=UTF-8
  • http code : 200
  • header size : 419
  • request size : 138
  • filetime : -1
  • ssl verify result : 20
  • redirect count : 0
  • total time : 0.331791
  • namelookup time : 0.001084
  • connect time : 0.010286
  • pretransfer time : 0.036811
  • size upload : 0
  • size download : 87450
  • speed download : 263569
  • speed upload : 0
  • download content length : -1
  • upload content length : 0
  • starttransfer time : 0.313698
  • redirect time : 0
  • redirect url :
  • primary ip : 217.160.0.41
  • certinfo :
  • primary port : 443
  • local ip : 116.202.66.56
  • local port : 53804
  • http version : 3
  • protocol : 2
  • ssl verifyresult : 0
  • scheme : HTTPS
  • appconnect time us : 36668
  • connect time us : 10286
  • namelookup time us : 1084
  • pretransfer time us : 36811
  • redirect time us : 0
  • starttransfer time us : 313698
  • total time us : 331791

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 2.0 s
  • First Meaningful Paint
  • Speed Index 2.0 s
  • First CPU Idle
  • Time to Interactive 8.5 s
  • Max Potential First Input Delay 50 ms

Audit Data

Resources Summary

Aggregates all network requests and groups them by typeLearn More

Eliminate render-blocking resources

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

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

14 resources found

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

Minimize third-party usage

Third-party code blocked the main thread for 0 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

Total Blocking Time

0 ms

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

JavaScript execution time

0.2 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

40 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

Est savings of 59 KiB

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

Reduce unused CSS

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 1,463 KiB

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

Minimizes main-thread work

0.3 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

7 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

Avoids an excessive DOM size

81 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 0.4 s
  • First Meaningful Paint
  • Speed Index 0.5 s
  • First CPU Idle
  • Time to Interactive 1.6 s
  • Max Potential First Input Delay 80 ms

Audit Data

Resources Summary

Aggregates all network requests and groups them by typeLearn More

Eliminate render-blocking resources

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

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

14 resources found

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

Minimize third-party usage

Third-party code blocked the main thread for 50 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

Total Blocking Time

50 ms

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

JavaScript execution time

0.2 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

40 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

Est savings of 210 KiB

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

Reduce unused CSS

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 1,503 KiB

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

Minimizes main-thread work

0.4 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

7 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

Avoids an excessive DOM size

81 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