2.9 sec in total
265 ms
1.9 sec
701 ms
Click here to check amazing 02 content for United Kingdom. Otherwise, check out these important facts you probably never knew about 02.co.uk
Find exclusive offers and discover Switch Up, Flexible Superfast 5G Tariffs, Free Roaming & O2 Priority. Stay connected, wherever you are.
Visit 02.co.ukWe analyzed 02.co.uk page load time and found that the first response time was 265 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
02.co.uk performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value15.7 s
0/100
25%
Value12.1 s
4/100
10%
Value3,140 ms
2/100
30%
Value0.026
100/100
15%
Value24.5 s
0/100
10%
265 ms
78 ms
45 ms
39 ms
82 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 02.co.uk, 56% (52 requests) were made to O2.co.uk and 37% (34 requests) were made to Static-www.o2.co.uk. The less responsive or slowest element that took the longest time to load (984 ms) relates to the external source Static-www.o2.co.uk.
Page size can be reduced by 422.3 kB (14%)
3.0 MB
2.6 MB
In fact, the total size of 02.co.uk main page is 3.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 236.4 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 84.2 kB, which is 32% 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 236.4 kB or 88% of the original size.
Potential reduce by 81.2 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. 02 images are well optimized though.
Potential reduce by 98.5 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 98.5 kB or 14% of the original size.
Potential reduce by 6.2 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. 02.co.uk needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 12% of the original size.
Number of requests can be reduced by 46 (55%)
83
37
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 02. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
02.co.uk
265 ms
www.o2.co.uk
78 ms
combo
45 ms
main.css
39 ms
clay.css
82 ms
main.css
68 ms
combo
43 ms
js_loader_config
75 ms
combo
102 ms
combo
79 ms
combo
75 ms
js_bundle_config
74 ms
combo
101 ms
main.css
111 ms
combo
100 ms
o2main.css
115 ms
slick.css
101 ms
slick-theme.css
101 ms
main_o2.js
113 ms
lux.js
71 ms
hidden.module.css
368 ms
global-nav.min.css
373 ms
slick.css
731 ms
answers.css
61 ms
style.css
385 ms
answerstemplates.compiled.min.js
69 ms
answers.min.js
101 ms
global-nav-webpack.js
984 ms
lazyload.js
386 ms
load.js
375 ms
ae8bce7a-1e8b-8fb6-a203-11a55d1e05a5
86 ms
main.css
84 ms
main.css
85 ms
main.css
100 ms
staging.js
95 ms
staging_branch.js
104 ms
staging_version.js
115 ms
main.css
104 ms
main.css
107 ms
main.css
110 ms
main.css
109 ms
main.js
359 ms
aui_deprecated.css
72 ms
font_awesome.css
68 ms
arrow-down-white-574x2.png
47 ms
f17f5e75-9f73-d08e-cccb-d6c3749124b5
41 ms
785783d4-a264-eaea-8dfd-1dd9fbf41487
47 ms
4167ef1a-ca6c-d909-25eb-b47e60db4818
62 ms
6a5c915c-bb27-0906-cc5d-88bb5897a163
39 ms
ce9a6d92-69f9-17bb-5e2b-cd939162ff4b
39 ms
icons.png
35 ms
arrowbig.png
40 ms
quick-links-apple-1100.png
39 ms
quick-links-samsung-1100.png
39 ms
xiaomi-legacy-global-nav-170423_0.png
45 ms
quick-links-google-1100.png
44 ms
quick-links-sony-1100.png
48 ms
5g-why-o2-thumbnail-dark-140220.jpg
44 ms
why-o2-thumbnail-dark-260220.jpg
47 ms
global-nav-community-image-070519.jpg
471 ms
close_search.png
48 ms
spinner-trans20.gif
56 ms
find-a-store%402x_0.png
57 ms
check-network%402x_0.png
54 ms
my-o2%402x_0.png
82 ms
track-order%402x.png
60 ms
search%402x_0.png
60 ms
facebook%402x_0.png
64 ms
youtube%402x_0.png
65 ms
twitter%402x_0.png
74 ms
instagram%402x.png
72 ms
gtm.js
80 ms
frutiger-55roman.woff
535 ms
basket-item-574x2.png
10 ms
search-hover@2x.png
10 ms
frutiger-45light.woff
27 ms
frutiger-45light.woff
28 ms
o2-icon-font.ttf
51 ms
o2-icon-font.woff
51 ms
bfbe31f2-c705-d545-da23-d17214406222
41 ms
frutiger-65bold.woff
43 ms
frutiger-65bold.woff
43 ms
3dd09c63-e37b-00d8-74cd-1e46de8eee91
40 ms
64fe16df-8aff-3eb5-0b98-6aa549323c4c
40 ms
feac42b5-243f-1f67-780b-6713cc4a1045
142 ms
abbdee5f-03be-3827-2ed5-09224dabc6a4
105 ms
o2-flurry-bubbles.png
60 ms
3cb3f8f0-2e53-93ac-6f85-42594a345936
119 ms
arrow-fwd.png
120 ms
330c0922-25b0-6b3f-1617-47dc3b82c1ad
118 ms
3b597b19-4527-80c0-ed73-b64c5bccb4ff
119 ms
arrow-right.svg
117 ms
frutiger-55roman.woff
73 ms
02.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.
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
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
Image elements do not have [alt] attributes
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
02.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
Missing source maps for large first-party JavaScript
02.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 02.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 02.co.uk 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.
02.co.uk
Open Graph description is not detected on the main page of 02. 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: