6.8 sec in total
699 ms
5.9 sec
276 ms
Welcome to shop.o2.co.uk homepage info - get ready to check Shop O2 best content for United Kingdom right away, or after learning these important things about shop.o2.co.uk
Find O2 offers on iPhone, Samsung and more. Reduce your monthly bill by spreading the cost up to 36 months. Flex your data up or down monthly on Pay Monthly devices.
Visit shop.o2.co.ukWe analyzed Shop.o2.co.uk page load time and found that the first response time was 699 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
shop.o2.co.uk performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value17.2 s
0/100
25%
Value10.4 s
8/100
10%
Value1,010 ms
27/100
30%
Value0.176
68/100
15%
Value23.0 s
1/100
10%
699 ms
865 ms
49 ms
1656 ms
725 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Shop.o2.co.uk, 30% (34 requests) were made to Static-www.o2.co.uk and 3% (3 requests) were made to Assets.sitescdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source O2.co.uk.
Page size can be reduced by 366.6 kB (28%)
1.3 MB
954.6 kB
In fact, the total size of Shop.o2.co.uk main page is 1.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. 65% of websites need less resources to load. Javascripts take 497.3 kB which makes up the majority of the site volume.
Potential reduce by 279.9 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 92.3 kB, which is 29% 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 279.9 kB or 89% of the original size.
Potential reduce by 27.6 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. Shop O2 images are well optimized though.
Potential reduce by 52.9 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 52.9 kB or 11% 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. Shop.o2.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 53 (51%)
103
50
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shop 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 20 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
shop
699 ms
combo
865 ms
main.css
49 ms
clay.css
1656 ms
main.css
725 ms
combo
321 ms
js_loader_config
82 ms
combo
585 ms
combo
996 ms
combo
2259 ms
js_bundle_config
651 ms
combo
928 ms
main.css
1325 ms
combo
1123 ms
o2main.css
1439 ms
slick.css
1016 ms
slick-theme.css
1094 ms
utag.sync.js
104 ms
main_o2.js
1195 ms
trustev.min.js
50 ms
lux.js
71 ms
hidden.module.css
164 ms
global-nav.min.css
191 ms
slick.css
1191 ms
answers.css
64 ms
style.css
203 ms
answerstemplates.compiled.min.js
94 ms
answers.min.js
103 ms
global-nav-webpack.js
225 ms
lazyload.js
203 ms
load.js
238 ms
ae8bce7a-1e8b-8fb6-a203-11a55d1e05a5
858 ms
main.css
1555 ms
main.css
1576 ms
staging.js
1460 ms
staging_branch.js
1895 ms
staging_version.js
1723 ms
main.css
1721 ms
main.css
1816 ms
main.css
1863 ms
main.css
1978 ms
main.css
2313 ms
main.js
2313 ms
icons.png
63 ms
arrowbig.png
63 ms
quick-links-apple-1100.png
64 ms
quick-links-samsung-1100.png
408 ms
xiaomi-legacy-global-nav-170423_0.png
62 ms
quick-links-google-1100.png
152 ms
quick-links-sony-1100.png
65 ms
5g-why-o2-thumbnail-dark-140220.jpg
64 ms
why-o2-thumbnail-dark-260220.jpg
65 ms
global-nav-community-image-070519.jpg
151 ms
close_search.png
151 ms
spinner-trans20.gif
150 ms
find-a-store%402x_0.png
152 ms
check-network%402x_0.png
154 ms
my-o2%402x_0.png
152 ms
track-order%402x.png
150 ms
search%402x_0.png
150 ms
facebook%402x_0.png
154 ms
youtube%402x_0.png
152 ms
twitter%402x_0.png
152 ms
instagram%402x.png
153 ms
827a2a9e-b4aa-08bd-47c0-7727aa47371f
404 ms
07fef0a8-7551-6fb5-a35e-fc0c1bc2998a
405 ms
33efd73b-df86-2807-1be8-af116e8a050c
404 ms
8a39ebe4-fea7-71ec-6a4a-21a81ec9490c
402 ms
392fee07-8846-4e00-0169-4f826de713cd
402 ms
047d9d94-948f-1ca3-e14b-9af5ac1d8230
59 ms
a665f176-d1ac-5d68-e11c-7eeca95d38bb
402 ms
a8b440ba-3713-b8ef-8458-46d3197e4d18
742 ms
2a5da476-c568-62ee-8b58-4fc9d9d45d07
743 ms
3264c69b-12e2-2fb8-100b-648c16421c11
745 ms
8c8b5a4a-9f3f-5b19-9c8e-1f785d9119c8
839 ms
0eba43a6-500f-3333-3e20-5401d51315f2
461 ms
78f980c9-e104-b768-c3f3-e9bb4a14a625
833 ms
9b7949be-0f88-dfc8-4684-386665385d0e
744 ms
a217c7ce-a8fb-5cd2-6c79-faf3d404a3f2
742 ms
37511987-41ae-fb79-8b8f-ace50b4b31b0
847 ms
c6b7a32c-9602-06ee-8c50-29c0bbaabb28
1089 ms
81205bca-6456-ac9c-00e1-e270b746c9bd
1197 ms
6af6c655-3cdd-8199-2308-aec029be6e5c
923 ms
utag.js
145 ms
frutiger-55roman.woff
1685 ms
basket-item-574x2.png
15 ms
search-hover@2x.png
219 ms
frutiger-45light.woff
206 ms
frutiger-45light.woff
1559 ms
o2-icon-font.ttf
207 ms
o2-icon-font.woff
1767 ms
promo-cta-arrow.png
693 ms
label-xxl-shadow1100.png
801 ms
label-xxl-line1100.png
802 ms
frutiger-55roman.woff
276 ms
o2-flurry-bubbles.png
97 ms
aab3fb55-38d1-eaf2-1191-f4e89a9ea345
347 ms
fadeda15-7a36-997b-427e-d5e6fe70e11d
343 ms
carousel-prev.png
346 ms
carousel-next.png
347 ms
frutiger-65bold.woff
36 ms
frutiger-65bold.woff
384 ms
e875e6d5-9756-f273-2c29-fd6ee507b487
307 ms
c14eab98-5ce3-afdd-022e-8f44a464bb66
442 ms
43e9eb63-6415-8015-63b0-ac3a2dfa8ab2
430 ms
e46aa662-c964-c930-c0af-04acba328f53
430 ms
b58f7a0c-c16a-44cc-a4ce-4dbd59be73a5
257 ms
d31fcbef-8198-d692-5fda-26172689b9d3
571 ms
c4835733-70b1-93f5-6c7d-92ad10d287f8
529 ms
6f142417-c5dc-5198-ad84-88942d71a715
610 ms
d50e9a14-fc6f-0e79-437a-70b78b9ab424
698 ms
61895fc2-2247-982f-a9ad-fc06ac659ed7
796 ms
bd3f44a6-b10f-e395-7792-504656c6c487
741 ms
shop.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.
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
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
shop.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
Missing source maps for large first-party JavaScript
shop.o2.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Shop.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 Shop.o2.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.
shop.o2.co.uk
Open Graph description is not detected on the main page of Shop 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: