Google Pagespeed Insights Checker

Arama motoru optimizasyonu

Sayfa Hız Testi Detaylı Pagespeed Insights Checker


Bir URL girin



Hakkında Sayfa Hız Testi Detaylı Pagespeed Insights Checker

Detaylı sayfa hız testi ile sayfa hızınızı belirleyin ve web sitenizi yavaşlatan adımları tespit ederek hataları giderin. Web sitenizin hızı google sıralamanızda büyük önem taşıyacaktır. Ayrıca diğer seo araçları ile web sitenizi en iyi şekilde düzenleyin.

Sayfa Hız Testi - Örnek Sonuç Görünümü

 

Final URL https://ask4seo.com/
Loading Experience  
Performance Score 93
Warnings - The page may not be loading as expected because your test URL (http://ask4seo.com/) was redirected to https://ask4seo.com/. Try testing the second URL directly.
 
Tested Mode Desktop
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/81.0.4044.108 Safari/537.36
Screenshot Web Site Görüntünüz

Details

Title Description Score Suggestion
Defer offscreen images 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). 100  
Remove unused JavaScript Remove unused JavaScript to reduce bytes consumed by network activity. [Learn more](https://web.dev/remove-unused-code/). 93 Potential savings of 127 KB
Max Potential First Input Delay 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). 100 40 ms
Enable text compression 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). 100  
Use video formats for animated content 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) 100  
JavaScript execution time 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/bootup-time). 99 0.6 s
Remove unused CSS 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). 97 Potential savings of 31 KB
Serve images in next-gen formats 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). 87 Potential savings of 123 KB
Avoids an excessive DOM size 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). 99 521 elements
Efficiently encode images Optimized images load faster and consume less cellular data. [Learn more](https://web.dev/uses-optimized-images). 100  
Largest Contentful Paint Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint) 73 1.7 s
First Contentful Paint First Contentful Paint marks the time at which the first text or image is painted. [Learn more](https://web.dev/first-contentful-paint). 97 0.7 s
Minimizes main-thread work 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) 100 0.9 s
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](https://web.dev/render-blocking-resources). 93 Potential savings of 80 ms
Avoids enormous network payloads Large network payloads cost users real money and are highly correlated with long load times. [Learn more](https://web.dev/total-byte-weight). 100 Total size was 995 KB
Minify CSS Minifying CSS files can reduce network payload sizes. [Learn more](https://web.dev/unminified-css). 100  
Estimated Input Latency 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). 100 10 ms
Time to Interactive Time to interactive is the amount of time it takes for the page to become fully interactive. [Learn more](https://web.dev/interactive). 100 0.7 s
Serve static assets with an efficient cache policy A long cache lifetime can speed up repeat visits to your page. [Learn more](https://web.dev/uses-long-cache-ttl). 63 75 resources found
Preload key requests Consider using `` to prioritize fetching resources that are currently requested later in page load. [Learn more](https://web.dev/uses-rel-preload). 100  
First CPU Idle 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). 100 0.7 s
Cumulative Layout Shift Cumulative Layout Shift measures the movement of visible elements within the viewport. [Learn more](https://web.dev/cls). 100 0.028
Properly size images Serve images that are appropriately-sized to save cellular data and improve load time. [Learn more](https://web.dev/uses-responsive-images). 97 Potential savings of 28 KB
Preconnect to required origins Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. [Learn more](https://web.dev/uses-rel-preconnect). 100  
Minify JavaScript Minifying JavaScript files can reduce payload sizes and script parse time. [Learn more](https://web.dev/unminified-javascript). 100  
First Meaningful Paint First Meaningful Paint measures when the primary content of a page is visible. [Learn more](https://web.dev/first-meaningful-paint). 97 0.7 s
Speed Index Speed Index shows how quickly the contents of a page are visibly populated. [Learn more](https://web.dev/speed-index). 98 1.0 s
Avoid multiple page redirects Redirects introduce additional delays before the page can be loaded. [Learn more](https://web.dev/redirects). 100 Potential savings of 190 ms
Total Blocking Time 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). 100 0 ms