4.4 sec in total
292 ms
3.9 sec
230 ms
Visit simpleomobile.fr now to see the best up-to-date Simpleomobile content and also check out these interesting facts you probably never knew about simpleomobile.fr
Forfait appels illimités + 3Go à 6,99€/mois !
Visit simpleomobile.frWe analyzed Simpleomobile.fr page load time and found that the first response time was 292 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
simpleomobile.fr performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value7.4 s
4/100
25%
Value4.0 s
80/100
10%
Value170 ms
93/100
30%
Value0.023
100/100
15%
Value7.0 s
53/100
10%
292 ms
771 ms
602 ms
600 ms
764 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Simpleomobile.fr, 70% (82 requests) were made to Medias.lapostemobile.fr and 17% (20 requests) were made to Lapostemobile.fr. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Medias.lapostemobile.fr.
Page size can be reduced by 477.7 kB (28%)
1.7 MB
1.3 MB
In fact, the total size of Simpleomobile.fr main page is 1.7 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 45.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. This page needs HTML code to be minified as it can gain 8.8 kB, which is 16% 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 45.6 kB or 80% of the original size.
Potential reduce by 18.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. Simpleomobile images are well optimized though.
Potential reduce by 248.3 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 248.3 kB or 63% of the original size.
Potential reduce by 165.5 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. Simpleomobile.fr needs all CSS files to be minified and compressed as it can save up to 165.5 kB or 85% of the original size.
Number of requests can be reduced by 73 (65%)
113
40
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simpleomobile. 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 14 to 1 for CSS and as a result speed up the page load time.
simpleomobile.fr
292 ms
www.lapostemobile.fr
771 ms
structure.css
602 ms
common.css
600 ms
components.css
764 ms
blocks.css
863 ms
custom.css
618 ms
univers.css
611 ms
serieLimitee.css
681 ms
actu-lpm.css
680 ms
odr.css
692 ms
localisation.css
707 ms
transverse-PC.css
842 ms
page_statique.css
762 ms
pcbn.css
1101 ms
shadowbox.css
795 ms
btn_ok_01.gif
185 ms
btn_ok_03.gif
193 ms
logo-v2.png
923 ms
arrow_menu_5a.png
841 ms
arrow_menu_5b.png
884 ms
layer_3_offre.png
1083 ms
btn_decouvrir-box-fibre.png
921 ms
jquery-1.6.2.min.js
1065 ms
scripts-v1.js
885 ms
slides.min.jquery.js
914 ms
icono_4g_small.gif
103 ms
header-v2.png
88 ms
separ-menu.png
86 ms
arrow-header-nav.png
88 ms
bg-param-mobile.png
89 ms
picto-activation.png
88 ms
param-mobile.png
92 ms
btn-espace-client.png
168 ms
ombre-header.png
169 ms
slider-0.jpg
337 ms
slider-1.jpg
253 ms
slider-2.jpg
261 ms
slider-4.jpg
584 ms
topHome_corners.png
248 ms
banniere-hp.jpg
251 ms
bg-bt-menu-hp-off.jpg
332 ms
arrow_menu_8.png
334 ms
arrow_menu_2.png
334 ms
arrow_menu_1.png
346 ms
arrow_menu_quatro.png
415 ms
7978.png
420 ms
8069.png
420 ms
8016.png
418 ms
8063.png
432 ms
8066.png
499 ms
8062.png
501 ms
hp_arr_prev.png
503 ms
hp_arr_next.png
502 ms
bt_gauche.gif
519 ms
bt_link_degrade.gif
582 ms
bt_droite.gif
584 ms
visuel_coupdecoeur_sans.jpg
667 ms
fd_bt_savoirplus.png
584 ms
hp_push_1.jpg
605 ms
forfaits-odr-resiliation.jpg
670 ms
icono_gps_small.gif
94 ms
icono_mpx_small.gif
98 ms
icono_video-hd_small.gif
189 ms
icono_carte-memoire_small.gif
187 ms
icono_tactile_small.gif
189 ms
icono_wifi_small.gif
193 ms
icono_mp3_small.gif
193 ms
icono_bluetooth_small.gif
194 ms
icono_flash_small.gif
279 ms
icono_player-video_small.gif
288 ms
icono_video_small.gif
281 ms
imprimer.png
288 ms
facebook-footer.png
291 ms
twitter-footer.png
289 ms
payement-securise.png
371 ms
hp_push_5_1.jpg
637 ms
hp_push_3.jpg
623 ms
jquery-1.4.4.min.js
671 ms
jquery-ui-1.8.7.custom.min.js
696 ms
widget.js
667 ms
Slider.js
678 ms
lapostemobile.js
677 ms
cb3620fr.js
676 ms
lpm.js
670 ms
toggle.js
669 ms
hp_push_5_3.jpg
592 ms
picto_li_one.png
590 ms
picto_li_two.png
657 ms
picto_li_three.png
654 ms
picto_li_four.png
603 ms
picto_li_five.png
601 ms
picto_li_six.png
602 ms
bandeau-hp.jpg
601 ms
mobiles-appli-hp.png
604 ms
picto_link_footer.png
130 ms
analytics.js
64 ms
gtm.js
101 ms
btn_ok_02.gif
115 ms
sliderPreviousButton.png
98 ms
sliderNextButton.png
100 ms
pauseButton.png
99 ms
playButton.png
99 ms
7978.png
135 ms
loading.gif
164 ms
collect
42 ms
conversion.js
30 ms
adperf_conversion.js
29 ms
adperf_conversion.js
43 ms
wreport_wcm.js
25 ms
comptage_wreport.fcgi
175 ms
comptage_wreport.fcgi
171 ms
dispatch.fcgi
355 ms
dispatch.fcgi
519 ms
activity;src=4301769;type=invmedia;cat=2q1v5q0b;ord=2183648962527.5134
33 ms
activity;src=4390938;type=invmedia;cat=nQGxzjy9;ord=6397683762479.573
37 ms
wamfactory.min.js
165 ms
simpleomobile.fr accessibility score
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.
simpleomobile.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
simpleomobile.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Simpleomobile.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Simpleomobile.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.
simpleomobile.fr
Open Graph description is not detected on the main page of Simpleomobile. 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: