5.4 sec in total
430 ms
4.8 sec
172 ms
Click here to check amazing Static O2 content for United Kingdom. Otherwise, check out these important facts you probably never knew about static.o2.co.uk
Visit static.o2.co.ukWe analyzed Static.o2.co.uk 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.
static.o2.co.uk performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value10.2 s
0/100
25%
Value10.0 s
9/100
10%
Value330 ms
75/100
30%
Value0.023
100/100
15%
Value9.1 s
33/100
10%
430 ms
1500 ms
205 ms
86 ms
170 ms
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 Static.o2.co.uk, 30% (14 requests) were made to Mymobile.o2.co.uk and 4% (2 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Mymobile.o2.co.uk.
Page size can be reduced by 1.0 MB (75%)
1.4 MB
340.1 kB
In fact, the total size of Static.o2.co.uk 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.
Potential reduce by 250.3 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. 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.
Potential reduce by 2.7 kB
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.
Potential reduce by 289.7 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 289.7 kB or 67% of the original size.
Potential reduce by 476.6 kB
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. Static.o2.co.uk needs all CSS files to be minified and compressed as it can save up to 476.6 kB or 88% of the original size.
Number of requests can be reduced by 32 (78%)
41
9
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.
static.o2.co.uk
430 ms
publichome
1500 ms
satelliteLib-0f7d9589551ed7071db2509e1b92aadeff17ecd3.js
205 ms
sha256.js
86 ms
analytics-page-data.js
170 ms
modernizr.min.js
379 ms
fonts.css
410 ms
migrated-consumer-desktop_all-modules.css
593 ms
migrated-consumer-desktop.css
431 ms
legacy-app-overrides-to-support-new-header-footer.css
426 ms
application.css
416 ms
reskin-style.css
582 ms
mbox.js
399 ms
jquery.tools.min.js
508 ms
jquery.application.js
322 ms
cookie.js
121 ms
application.js
320 ms
bi-survey-edigital-research.js
397 ms
o2.min.js
455 ms
id
42 ms
id
25 ms
target.js
242 ms
standard
363 ms
legacy-app-overrides-to-support-new-header-footer.css
87 ms
legacy-app-overrides-to-support-new-header-footer.css
96 ms
tab-bg-sel.gif
85 ms
tool-icon-search-sprite.png
90 ms
toolbar-sitetabs.png
85 ms
logo-o2.svg
91 ms
primary-nav-border.png
86 ms
logo-telefonica.svg
86 ms
inputbtn-bg.gif
169 ms
footer-gradient-mobile.png
127 ms
footer-bubbles.png
140 ms
footer-list-splitter.png
141 ms
footer-sprite-social-icons.png
142 ms
sprite-logo-telefonica.png
141 ms
myfamilybanner.jpg
337 ms
family-module-bg.gif
86 ms
frutiger-55roman.woff
312 ms
frutiger-45light.woff
377 ms
frutigerltstd-roman.woff
254 ms
frutiger-65bold.woff
399 ms
analytics.js
59 ms
s-code-contents-d2e3f58d3f18050c00cfdd4af1ece2cc04457830.js
89 ms
collect
12 ms
s44683261793106
9 ms
static.o2.co.uk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Definition list items are not wrapped in <dl> elements
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
static.o2.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
static.o2.co.uk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Static.o2.co.uk 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 Static.o2.co.uk 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.
static.o2.co.uk
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: