Tools & Wizards About Us
ookla.net screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

ookla.net

Ookla® | Network intelligence to enable modern connectivity

Page Load Speed

992 ms in total

First Response

17 ms

Resources Loaded

517 ms

Page Rendered

458 ms

ookla.net screenshot

About Website

Welcome to ookla.net homepage info - get ready to check Ookla best content right away, or after learning these important things about ookla.net

Ookla® is a global leader in network intelligence and connectivity insights. Explore solutions for consumers, operators, businesses, non-profits, and more.

Visit ookla.net

Key Findings

We analyzed Ookla.net page load time and found that the first response time was 17 ms and then it took 975 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

ookla.net performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

www.ookla.com

17 ms

gtm.js

281 ms

zdconsent.js

23 ms

6583452.js

71 ms

styles.css

7 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ookla.net, 6% (3 requests) were made to Use.typekit.net and 2% (1 request) were made to Sgtm.ookla.com. The less responsive or slowest element that took the longest time to load (281 ms) relates to the external source Sgtm.ookla.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 581.8 kB (18%)

Content Size

3.3 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ookla.net main page is 3.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 87.0 kB

  • Original 109.1 kB
  • After minification 95.8 kB
  • After compression 22.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 13.3 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 87.0 kB or 80% of the original size.

Image Optimization

-15%

Potential reduce by 465.7 kB

  • Original 3.1 MB
  • After minification 2.6 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Ookla needs image optimization as it can save up to 465.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-41%

Potential reduce by 29.0 kB

  • Original 71.5 kB
  • After minification 49.6 kB
  • After compression 42.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 29.0 kB or 41% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered.

Requests Breakdown

Number of requests can be reduced by 12 (24%)

Requests Now

51

After Optimization

39

  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ookla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.ookla.com

www.ookla.com

17 ms

gtm.js

gtm.js

281 ms

zdconsent.js

zdconsent.js

23 ms

6583452.js

6583452.js

71 ms

styles.css

styles.css

7 ms

vvd2klp.css

vvd2klp.css

177 ms

bundle.js

bundle.js

15 ms

wp-block-datatable.js

wp-block-datatable.js

20 ms

wp-block-toggle-blocks.js

wp-block-toggle-blocks.js

21 ms

wp-block-vertical-tabs.js

wp-block-vertical-tabs.js

19 ms

tabbed-cta.js

tabbed-cta.js

20 ms

main-nav.js

main-nav.js

20 ms

banner.js

banner.js

36 ms

6583452.js

6583452.js

47 ms

fb.js

fb.js

51 ms

p.css

p.css

25 ms

speedtest-insights-featured-article@2x.png

speedtest-insights-featured-article@2x.png

13 ms

insight.min.js

insight.min.js

53 ms

product_1.png

product_1.png

8 ms

Speedtest-CTA.png

Speedtest-CTA.png

6 ms

product_applestore.png

product_applestore.png

6 ms

product_applestore_light.png

product_applestore_light.png

6 ms

product_playstore.png

product_playstore.png

8 ms

product_playstore_light.png

product_playstore_light.png

7 ms

speedtest_website_bw.png

speedtest_website_bw.png

8 ms

speedtest_website.png

speedtest_website.png

13 ms

Group-1096.png

Group-1096.png

13 ms

downdetector_bw.png

downdetector_bw.png

9 ms

downdetector.png

downdetector.png

9 ms

Group-1097.png

Group-1097.png

9 ms

ekahayu_website_bg.png

ekahayu_website_bg.png

9 ms

ekahayu_website.png

ekahayu_website.png

13 ms

Group-1098.png

Group-1098.png

17 ms

rootmetrics_website_bw.png

rootmetrics_website_bw.png

12 ms

rootmetrics_website.png

rootmetrics_website.png

13 ms

Group-1099.png

Group-1099.png

16 ms

speedtest_connectivity_reports_header_508x191.png

speedtest_connectivity_reports_header_508x191.png

17 ms

Speedtest-Default.png

Speedtest-Default.png

14 ms

Speedtest-Hover.png

Speedtest-Hover.png

14 ms

Screenshot-2024-02-23-at-12.51.11%E2%80%AFPM.png

Screenshot-2024-02-23-at-12.51.11%E2%80%AFPM.png

18 ms

DD-Default.png

DD-Default.png

16 ms

DD-Hover.png

DD-Hover.png

18 ms

RootMetrics-Default.png

RootMetrics-Default.png

16 ms

Rootmetrics-Hover.png

Rootmetrics-Hover.png

20 ms

Ekahau-Default.png

Ekahau-Default.png

19 ms

Ekahau-Hover.png

Ekahau-Hover.png

18 ms

vodafone_case.png

vodafone_case.png

50 ms

bnet_case.png

bnet_case.png

50 ms

oecd_case.png

oecd_case.png

51 ms

enterprise_case.png

enterprise_case.png

50 ms

speedtest_connectivity_reports_header_629x330_2.png

speedtest_connectivity_reports_header_629x330_2.png

49 ms

d

d

19 ms

d

d

26 ms

insight_tag_errors.gif

insight_tag_errors.gif

169 ms

Accessibility Review

ookla.net accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

ookla.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ookla.net SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ookla.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ookla.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

ookla.net

Open Graph data is detected on the main page of Ookla. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: