E621.net - SEO Checker - Website Review (2024)

Reduce unused CSSPotential savings of 33KiB

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

Time to Interactive0.5s

Time to Interactive is the amount of time it takes for the page to become fully interactive

Avoid large layout shifts1 layout shift found

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

Max Potential First Input Delay60ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

Serve images in next-gen formatsPotential savings of 170KiB

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Largest Contentful Paint0.9s

Largest Contentful Paint marks the time at which the largest text or image is painted

Network Round Trip Times0ms

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

Initial server response time was shortRoot document took 290ms

Keep the server response time for the main document short because all other requests depend on it

Avoid serving legacy JavaScript to modern browsersPotential savings of 0KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

Avoids an excessive DOM size62 elements

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)

Serve static assets with an efficient cache policy10 resources found

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

Largest Contentful Paint element880ms

This is the largest contentful element painted within the viewport

Avoids enormous network payloadsTotal size was 431KiB

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

First Contentful Paint0.4s

First Contentful Paint marks the time at which the first text or image is painted

Server Backend Latencies270ms

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

First Meaningful Paint0.4s

First Meaningful Paint measures when the primary content of a page is visible

Minimizes main-thread work0.2s

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

JavaScript execution time0.1s

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

Speed Index0.6s

Speed Index shows how quickly the contents of a page are visibly populated

Avoid long main-thread tasks1 long task found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Cumulative Layout Shift0.001

Cumulative Layout Shift measures the movement of visible elements within the viewport

Reduce unused JavaScriptPotential savings of 108KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

Total Blocking Time10ms

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

Speed Index2.1s

Speed Index shows how quickly the contents of a page are visibly populated

Avoid long main-thread tasks4 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Efficiently encode imagesPotential savings of 196KiB

Optimized images load faster and consume less cellular data

Avoid large layout shifts1 layout shift found

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)

Avoids enormous network payloadsTotal size was 505KiB

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

Largest Contentful Paint element3,800ms

This is the largest contentful element painted within the viewport

Cumulative Layout Shift0.007

Cumulative Layout Shift measures the movement of visible elements within the viewport

Reduce unused JavaScriptPotential savings of 108KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

Avoid serving legacy JavaScript to modern browsersPotential savings of 0KiB

Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers

Total Blocking Time130ms

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

Avoids an excessive DOM size62 elements

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)

Serve images in next-gen formatsPotential savings of 242KiB

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Serve static assets with an efficient cache policy10 resources found

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

Reduce unused CSSPotential savings of 33KiB

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

Document uses legible font sizes93.25% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

JavaScript execution time0.4s

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

Largest Contentful Paint3.8s

Largest Contentful Paint marks the time at which the largest text or image is painted

Max Potential First Input Delay300ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task

Initial server response time was shortRoot document took 270ms

Keep the server response time for the main document short because all other requests depend on it

First Contentful Paint2.1s

First Contentful Paint marks the time at which the first text or image is painted

First Meaningful Paint2.2s

First Meaningful Paint measures when the primary content of a page is visible

Network Round Trip Times0ms

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

Time to Interactive2.8s

Time to Interactive is the amount of time it takes for the page to become fully interactive

Server Backend Latencies200ms

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

Minimizes main-thread work1.2s

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

Title Website

Warning! Your title is not optimized

Description Website

Warning! Your description is not optimized

Robots.txt

Warning! Your site not have a robots.txt file

Sitemap.xml

Warning! Not found a sitemap file for your website

SSL Secure

Congratulations! Your site have Support to HTTPS

Headings

Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines

Blacklist

Congratulations! Your site is not listed in a blacklist

W3C Validator

Warning! Your site have errors W3C

Accelerated Mobile Pages (AMP)

Warning! Your site not have AMP Version

Domain Authority

Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.

GZIP Compress

Warning! Your site not is compressed, this can make slower response for the visitors

Favicon

Congratulations! Your website appears to have a favicon.

Broken Links

Congratulations! You not have broken linksView links