Analyze O2 | My device

Page load speed analysis

  • 57/100

    Normal result
  • 4

    Successful tests
  • 4

    Failed tests
  • First response

    430 ms

  • Resources loaded

    4.8 sec

  • Page rendered

    172 ms

  • Total page load time

    5.4 sec

Click here to check amazing Static O2 content for United Kingdom. Otherwise, check out these important facts you probably never knew about

We analyzed page load time and found that the first response time was 430 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Page optimization

  • HTML 297.7 kB
    Images 85.9 kB
    Javascripts 437.0 kB
    CSS 544.1 kB

    In fact, the total size of main page is 1.4 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. 30% of websites need less resources to load. CSS take 544.1 kB which makes up the majority of the site volume.

    • Original 297.7 kB
    • After minification 291.8 kB
    • After compression 47.4 kB

    HTML optimization

    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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 250.3 kB or 84% of the original size.

    • Original 85.9 kB
    • After optimization 83.2 kB

    Image optimization

    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. Static O2 images are well optimized though.

    • Original 437.0 kB
    • After minification 427.6 kB
    • After compression 132.0 kB

    JavaScript optimization

    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 305.0 kB or 70% of the original size.

    • Original 544.1 kB
    • After minification 472.8 kB
    • After compression 67.5 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 476.6 kB or 88% of the original size.

Network requests diagram

  • publichome
  • satelliteLib-0f7d9589551ed7071db2509e1b92aadeff17ecd3.js
  • sha256.js
  • analytics-page-data.js
  • modernizr.min.js
  • fonts.css
  • migrated-consumer-desktop_all-modules.css
  • migrated-consumer-desktop.css
  • legacy-app-overrides-to-support-new-header-footer.css
  • application.css
  • reskin-style.css
  • mbox.js
  • jquery.application.js
  • cookie.js
  • application.js
  • bi-survey-edigital-research.js
  • o2.min.js
  • id
  • id
  • target.js
  • standard
  • legacy-app-overrides-to-support-new-header-footer.css
  • legacy-app-overrides-to-support-new-header-footer.css
  • tab-bg-sel.gif
  • tool-icon-search-sprite.png
  • toolbar-sitetabs.png
  • logo-o2.svg
  • primary-nav-border.png
  • logo-telefonica.svg
  • inputbtn-bg.gif
  • footer-gradient-mobile.png
  • footer-bubbles.png
  • footer-list-splitter.png
  • footer-sprite-social-icons.png
  • sprite-logo-telefonica.png
  • myfamilybanner.jpg
  • family-module-bg.gif
  • frutiger-55roman.woff
  • frutiger-45light.woff
  • frutigerltstd-roman.woff
  • frutiger-65bold.woff
  • analytics.js
  • s-code-contents-d2e3f58d3f18050c00cfdd4af1ece2cc04457830.js
  • collect
  • s44683261793106

Our browser made a total of 47 requests to load all elements on the main page. We found that 49% of them (23 requests) were addressed to the original, 30% (14 requests) were made to and 4% (2 requests) were made to The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source

Additional info on


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









Possible request optimization











Normal result


As for redirects, our browser was forwarded to before it reached this domain.

IP address uses IP addresses which are currently shared with 14 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 60
A 60
A 60
A 60
NS 86400

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 54.9% of all visits is United Kingdom. It lies approximately 4610 miles away from the server location (United States) and such a long distance can negatively affect website speed, as it takes some time for data to travel back and forth between those places. That’s why one of the best ways to speed up page load time for the majority of users is moving the server to United Kingdom or just closer to the user base.

Poor result

Poor result

Social Sharing Optimization

Open Graph description is not detected on the main page of Static O2. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Language and encoding

Poor result


N/A  language flag


EN en language flag





Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Share this report in social media

Analyze another website