Clicky

Why Is Gizmodo.com Slow? Here Are The Reasons

Gizmodo.com is a popular website in the category. According to the latest CWVIQ speed report, Gizmodo.com took 0.02 seconds to load the page. Anything over 5 seconds means that the website is too slow to load.

A slow load time could be due to a lot of things – poor network connectivity at your end, an unreliable hosting server, or a poorly optimized webpage.

First off, let’s look at a breakup of the loading time.

DNS Lookup Time

(Time taken to lookup the IP address of the server)

12.59 ms
TCP Connection

(Time taken to establish a connection between your server and the server where Gizmodo.com is hosted)

1.66 ms
SSL Handshake

(Time taken to verify server credentials by comparing public key with its digital signature)

0.04 ms
Server Processing

(Time it takes for the website’s server to process your request)

9.88 ms
Content Transfer

(Time it takes for the requested data to be transmitted to your server)

0.05 ms
TOTAL TIME 0.02 seconds

A high value for DNS lookup or TCP connection could be because of local settings, or internet connection.While a high server processing time or content transfer time could indicate issues with the website or its server.

We also studied the Gizmodo.com Lighthouse report to look at the site’s performance. Here is what we found.

Speed Index – Time for the page content to be visibly populated 5.4 s
Server response time 11 ms
First Meaningful Paint – Time for the viewable content to be rendered to the user 0.9 s

How To Make Gizmodo.com faster

Here are the top 17 ways to make Gizmodo.com faster.

1. Time to Interactive – 13.23 seconds

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

2. Minimize main-thread work – 13.1 seconds

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

3. Reduce JavaScript execution time – 6.9 seconds

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

4. Speed Index – 5.41 seconds

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

5. Reduce unused JavaScript – 1.53 seconds

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

6. Largest Contentful Paint – 1.17 seconds

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

7. Total Blocking Time – 1.07 seconds

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

8. First Contentful Paint – 0.92 seconds

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

9. First Meaningful Paint – 0.92 seconds

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

10. Serve images in next-gen formats – 0.56 seconds

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

11. Max Potential First Input Delay – 0.26 seconds

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

12. Avoid multiple page redirects – 0.23 seconds

Redirects introduce additional delays before the page can be loaded.

13. Enable text compression – 0.14 seconds

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

14. Efficiently encode images – 0.12 seconds

Optimized images load faster and consume less cellular data.

15. Minify JavaScript – 0.05 seconds

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

16. Properly size images – 0.04 seconds

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

17. Defer offscreen images – 0.04 seconds

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

In addition to these reasons, here are other ways to make Gizmodo.com faster.

Preconnect to required origins –

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.

Cumulative Layout Shift – 0.001

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

Avoid enormous network payloads – Total size was 5,204 KiB

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

Serve static assets with an efficient cache policy – 126 resources found

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

Avoid an excessive DOM size – 2,266 elements

A large DOM will increase memory usage, cause longer

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top