1.7 sec in total
266 ms
1.3 sec
190 ms
Visit selfone.fr now to see the best up-to-date Selfone content for France and also check out these interesting facts you probably never knew about selfone.fr
Selfone CMRP propose des solutions de communication des entreprises de demain : Téléphonie, Internet très haut débit, chat, vidéo ...
Visit selfone.frWe analyzed Selfone.fr page load time and found that the first response time was 266 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
selfone.fr performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value6.1 s
12/100
25%
Value10.3 s
8/100
10%
Value1,800 ms
10/100
30%
Value0.32
36/100
15%
Value12.8 s
13/100
10%
266 ms
82 ms
160 ms
161 ms
244 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 93% of them (56 requests) were addressed to the original Selfone.fr, 3% (2 requests) were made to V2.zopim.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (670 ms) belongs to the original domain Selfone.fr.
Page size can be reduced by 158.3 kB (37%)
431.1 kB
272.8 kB
In fact, the total size of Selfone.fr main page is 431.1 kB. 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 198.1 kB which makes up the majority of the site volume.
Potential reduce by 25.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 6.2 kB, which is 19% 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 25.8 kB or 81% of the original size.
Potential reduce by 4.3 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. Selfone images are well optimized though.
Potential reduce by 104.8 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 104.8 kB or 60% of the original size.
Potential reduce by 23.4 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. Selfone.fr needs all CSS files to be minified and compressed as it can save up to 23.4 kB or 87% of the original size.
Number of requests can be reduced by 36 (61%)
59
23
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Selfone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
selfone.fr
266 ms
style.css
82 ms
add-event.js
160 ms
fonctions.js
161 ms
jquery-1.6.2.min.js
244 ms
jquery-1.js
268 ms
jquery_002.js
177 ms
jquery_003.js
180 ms
jquery.js
238 ms
coda-slider.js
238 ms
fond.jpg
160 ms
ombre_milieu_content.png
160 ms
fond_bandeau_selfone.jpg
158 ms
selfone.png
157 ms
flag-france.jpg
159 ms
flag-belgique.jpg
155 ms
flag-suisse.jpg
160 ms
fond_menu.jpg
168 ms
numero-france.jpg
167 ms
numero-belge.jpg
174 ms
numero-portugal.jpg
173 ms
numero-canada.jpg
178 ms
numero-russie.jpg
241 ms
numero-chine.jpg
242 ms
numero-italie.jpg
241 ms
numero-us.jpg
259 ms
numero-suede.jpg
260 ms
numero-danemark.jpg
267 ms
numero-japon.jpg
309 ms
numero-royaume-unis.jpg
317 ms
numero-espagne.jpg
317 ms
numero-mexique.jpg
344 ms
numero-bresil.jpg
345 ms
numero-allemagne.jpg
355 ms
numero-paysbas.jpg
388 ms
numero-suisse.jpg
392 ms
partenaire_asterisk.jpg
394 ms
partenaire_ultimcore.jpg
431 ms
partenaire_cisco.jpg
433 ms
standard-entreprise-cisco.jpg
445 ms
devenir-revendeur.jpg
465 ms
forfait-illimite-fixe-mobile-fr.jpg
528 ms
btn_lien_140_big.png
452 ms
forfait-illimite-fixe-mobile-eu.jpg
670 ms
offre-adsl-pro.jpg
583 ms
btn_lien_140.png
513 ms
widget_v2.134.js
39 ms
ga.js
12 ms
__$$__stringtable_lang_fr.js
25 ms
__utm.gif
16 ms
fleche_nav.png
398 ms
fond_bloc_did_home.jpg
405 ms
fond_bloc_ipbx_home.jpg
476 ms
btn_lien_220.png
474 ms
fond_bloc_instal_pme.jpg
478 ms
fond_bloc_revendeur_ip.jpg
481 ms
ombre_bas_content.png
535 ms
ombre_haut_content.png
544 ms
engagements-selfone.jpg
554 ms
adsl-sdsl-pro.jpg
541 ms
selfone.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Links do not have a discernible 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
selfone.fr 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
Browser errors were logged to the console
Page has valid source maps
selfone.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
Tap targets are not sized appropriately
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Selfone.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Selfone.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.
selfone.fr
Open Graph description is not detected on the main page of Selfone. 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: