4.7 sec in total
265 ms
4.2 sec
231 ms
Click here to check amazing O2 content for France. Otherwise, check out these important facts you probably never knew about o2.fr
Leader des services à la personne depuis 1996. Plus de 350 agences en France. Prestations 100% personnalisées. -50% crédit d’impôt. Votre devis gratuit en ligne.
Visit o2.frWe analyzed O2.fr page load time and found that the first response time was 265 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
o2.fr performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value11.6 s
0/100
25%
Value8.4 s
18/100
10%
Value2,180 ms
6/100
30%
Value0.356
31/100
15%
Value13.6 s
11/100
10%
265 ms
358 ms
85 ms
219 ms
330 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 24% of them (25 requests) were addressed to the original O2.fr, 26% (27 requests) were made to D1oj1qx7ptn6u1.cloudfront.net and 8% (8 requests) were made to Asset.easydmp.net. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Blog.o2.fr.
Page size can be reduced by 912.0 kB (37%)
2.5 MB
1.6 MB
In fact, the total size of O2.fr main page is 2.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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 53.6 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 53.6 kB or 80% of the original size.
Potential reduce by 80.4 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. O2 images are well optimized though.
Potential reduce by 684.0 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 684.0 kB or 72% of the original size.
Potential reduce by 94.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. O2.fr needs all CSS files to be minified and compressed as it can save up to 94.1 kB or 87% of the original size.
Number of requests can be reduced by 35 (36%)
96
61
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 22 to 1 for JavaScripts and as a result speed up the page load time.
o2.fr
265 ms
www.o2.fr
358 ms
site.jsgz
85 ms
knacss.css
219 ms
style.css
330 ms
o2-devis-express.css
170 ms
jquery.min.js
50 ms
000ac0605704e8d954bef90645be0b3f.js
410 ms
o2-devis-express.js
250 ms
jquery.jsgz
630 ms
tracking.jsgz
166 ms
gtm.js
131 ms
dc.js
39 ms
conversion_async.js
16 ms
77 ms
__utm.gif
27 ms
__utm.gif
23 ms
30 ms
prototype.jsgz
196 ms
geolocAndWeather.php
256 ms
datacollect.php
240 ms
btn-open-o2.png
2074 ms
logo-o2.png
59 ms
datacollectSegment.php
230 ms
jevoislavieenmieux.png
54 ms
wdg-btn-rappel.jpg
52 ms
puce.gif
15 ms
coeur-left.png
56 ms
coeur-right.png
53 ms
focus-mr-201312_mini.jpg
51 ms
pave_actu_GE_200x160.jpg
56 ms
pave_actu_SE_200x160.jpg
57 ms
pave_actu_AVHA_200x160_mini.jpg
60 ms
pave_actu_IT_200x160.jpg
57 ms
vignette-sous-menu-jardi-aout-2015.jpg
115 ms
bulletop.png
59 ms
bullebottom.png
61 ms
arrow-right-o2.png
61 ms
arrow-left-o2.png
112 ms
chiffres-201501.jpg
115 ms
hpmag-reseau-o2_mini.jpg
114 ms
stan.jpg
114 ms
starekomi-gold.gif
114 ms
starekomi-half.gif
116 ms
hp-patron-incognito.jpg
119 ms
btn-facebook.png
116 ms
btn-twitter.png
118 ms
btn-youtube.png
114 ms
logo-nf-service.png
116 ms
logo-silver-eco.jpg
118 ms
fr.png
206 ms
gb.png
205 ms
Carrousel-site-O2-Patron-Incognito-1.jpg
386 ms
carousel-ptits-champions-VF.jpg
475 ms
Carrousel-HP_Univers-Jardi-Noel.jpg
491 ms
MR-fev-2016.jpg
584 ms
GE-fev-2016.jpg
675 ms
SE-fev-2016.png
759 ms
btn-close-formresa-orange.png
2064 ms
loader.gif
3065 ms
fbds.js
219 ms
createVisitorCookie.php
218 ms
1449237355btn-devis-express-green.gif
466 ms
Menu-1_MR.png
504 ms
Menu-1_GE.png
514 ms
Menu-1_SE.png
524 ms
Menu-1_HA.png
517 ms
Menu-1_IT.png
523 ms
Menu-1_JARDI.png
524 ms
1449226520btn-devis-express.gif
515 ms
bg-rappel-gratuit-4.png
472 ms
Essais4-Bouton-RG-New-Horaire.png
661 ms
1436964745bouton_Devis-express-vert.png
461 ms
1436964783bouton_Quit1-vert.png
475 ms
1444380793Logo_O2-RVB-2.png
466 ms
widget-ekomi.jpg
504 ms
bulle-blog.png
517 ms
puce-footer-blog.jpg
540 ms
chaletny.otf
562 ms
_xyN3apAT_yRRDeqB3sPRg.woff
119 ms
OsJ2DjdpjqFRVUSto6IffD8E0i7KZn-EPnyo3HZu7kw.woff
152 ms
_aijTyevf54tkVDLy-dlnD8E0i7KZn-EPnyo3HZu7kw.woff
156 ms
0ihfXUL2emPh0ROJezvraD8E0i7KZn-EPnyo3HZu7kw.woff
155 ms
com.jsgz
656 ms
site.jsgz
672 ms
bat.js
100 ms
emafunc.js
419 ms
oct.js
94 ms
empty.gif
166 ms
109 ms
adsct
92 ms
adsct
70 ms
dn_iframe.js
314 ms
ace
174 ms
dn.html
268 ms
asset
174 ms
dn.js
218 ms
get_delivery_data.php
331 ms
rteasdt.html
258 ms
script_graphinium.php
219 ms
retrieve.js
227 ms
retrieve_frame.html
220 ms
retrieve_ec.js
219 ms
23 ms
o2.fr 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
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
o2.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
o2.fr SEO score
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise O2.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that O2.fr 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.
o2.fr
Open Graph description is not detected on the main page of 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: