2.8 sec in total
412 ms
2.2 sec
225 ms
Click here to check amazing Webmap O2 content for United Kingdom. Otherwise, check out these important facts you probably never knew about webmap.o2.co.uk
Check your 2G, 3G, 4G and 5G network coverage with the O2 Coverage Checker. Includes call and mobile internet reception – as well as your nearest O2 Wifi hotspots.
Visit webmap.o2.co.ukWe analyzed Webmap.o2.co.uk page load time and found that the first response time was 412 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
webmap.o2.co.uk performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value11.8 s
0/100
25%
Value14.2 s
1/100
10%
Value10,610 ms
0/100
30%
Value0.469
18/100
15%
Value25.8 s
0/100
10%
412 ms
181 ms
7 ms
176 ms
177 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Webmap.o2.co.uk, 66% (37 requests) were made to Static.o2.co.uk and 16% (9 requests) were made to Cdn.spatialbuzz.com. The less responsive or slowest element that took the longest time to load (632 ms) relates to the external source Static.o2.co.uk.
Page size can be reduced by 987.3 kB (65%)
1.5 MB
529.0 kB
In fact, the total size of Webmap.o2.co.uk main page is 1.5 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. 45% of websites need less resources to load. Javascripts take 814.8 kB which makes up the majority of the site volume.
Potential reduce by 39.8 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 5.3 kB, which is 11% 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 39.8 kB or 83% of the original size.
Potential reduce by 18.0 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. Webmap O2 images are well optimized though.
Potential reduce by 562.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 562.4 kB or 69% of the original size.
Potential reduce by 367.1 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. Webmap.o2.co.uk needs all CSS files to be minified and compressed as it can save up to 367.1 kB or 88% of the original size.
Number of requests can be reduced by 34 (67%)
51
17
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webmap 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 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
webmap.o2.co.uk
412 ms
coveragechecker
181 ms
satelliteLib-0f7d9589551ed7071db2509e1b92aadeff17ecd3.js
7 ms
fonts.css
176 ms
base.css
177 ms
migrated-consumer-desktop_all-modules.css
346 ms
migrated-consumer-desktop.css
182 ms
modernizr.custom.js
183 ms
jquery-1.7.min.js
274 ms
coveragechecker.css
259 ms
bootstrap-core.js
255 ms
bootstrap-hdcv2-68AA7B45-iframe-init.js
256 ms
bootstrap-hdcoverage-v2-iframe.js
266 ms
o2.min.js
260 ms
eluminate.js
83 ms
analytics.js
262 ms
id
9 ms
id
6 ms
tool-icon-search-sprite.png
86 ms
jquery-1.8.3.min.js
245 ms
toolbar-sitetabs.png
86 ms
logo-o2.svg
95 ms
primary-nav-border.png
94 ms
logo-telefonica.svg
91 ms
bodybgr.png
93 ms
coveragemapdeco.png
312 ms
cgtitle.png
263 ms
question.png
172 ms
logos.jpg
262 ms
vshape.png
172 ms
lw-tugo.png
263 ms
lw-livestatus.png
262 ms
lw-faqs.png
263 ms
footer-gradient-mobile.png
337 ms
footer-bubbles.png
339 ms
footer-list-splitter.png
340 ms
footer-sprite-social-icons.png
341 ms
sprite-logo-telefonica.png
346 ms
s-code-contents-d2e3f58d3f18050c00cfdd4af1ece2cc04457830.js
27 ms
tool-icon-signin.png
360 ms
tool-icon-webchat.png
380 ms
tool-icon-storelocator.png
382 ms
nav-secondary-vertical-shadow.png
383 ms
nav-mobile-arrow-sprite.png
384 ms
item-border-bottom.png
390 ms
frutiger-55roman.woff
444 ms
frutiger-45light.woff
632 ms
frutiger-65bold.woff
550 ms
s31624560477212
6 ms
jquery.ba-postmessage.js
164 ms
hdcv2.html
179 ms
require.min.js
166 ms
config.js
165 ms
nr-476.min.js
17 ms
bootstrap-hdcoverage-v2-pub.js
306 ms
f0cf67e999
46 ms
webmap.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
webmap.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
webmap.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
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 Webmap.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 Webmap.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.
webmap.o2.co.uk
Open Graph description is not detected on the main page of Webmap 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: