Your Website Score is

Similar Ranking

87
.NET |---. CROSS-PLATFORM. OPEN SOURCE.
windows.net
87
CCM - ONLINE COMMUNITY
ccm.net
87
GOOGLE
google.fi
87
東洋経済オンライン | 経済ニュースの新基準
toyokeizai.net
87
店铺浏览-淘宝网
janeeyre.tmall.com
87
COMO CRIAR UM SITE GRÁTIS | DESCUBRA COMO CRIAR UM SITE GRÁTIS - WEBNODE
webnode.com.br
87
WELCOME TO PYTHON.ORG
python.org

Latest Sites

14
FINYA LIMITED
finyalimited.com
14
CADOCINVESTMENT.COM | AUSTRALIAN INVESTMENT COMPANY
cadocinvestment.com
14
NGF LEGAL – CORPORATE LAWYER AGENCY
ngflegal.com
14
GLOBAL LOGISTICS AUSTRALIA | GLOBAL LOGISTICS LIMITED
globallogisticslimited.com
50
THE GUY R COOK REPORT BLOG
guyrcook.com
26
CLOKIDS
clokids.shop

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

87 sfr.fr Last Updated: 12 months

Success 62% of passed verification steps
Warning 23% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 85%
Best Practices Desktop Score 92%
SEO Desktop Score 91%
Progressive Web App Desktop Score 58%
Performance Mobile Score 30%
Best Practices Mobile Score 85%
SEO Mobile Score 90%
Progressive Web App Mobile Score 59%
Page Authority Authority 58%
Domain Authority Domain Authority 89%
Moz Rank 5.8/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 76 Characters
SFR | TÉLÉPHONE, FORFAIT MOBILE, INTERNET + FIBRE, SPORT, PLAY, PRESSE, NEWS
Meta Description 182 Characters
Découvrez les offres Mobile, TV, Internet et Fibre de SFR. Choisissez le forfait qui répond à vos besoins et retrouvez aussi le meilleur des contenus SFR Sport, SFR Play, SFR Presse.
Effective URL 18 Characters
https://www.sfr.fr
Excerpt Page content
SFR | Téléphone, Forfait Mobile, Internet + Fibre, Sport, Play, Presse, News ...
Meta Keywords 3 Detected
Keywords Cloud Density
mobile23 avec17 vous16 offres15 votre12 mois11 sport9 téléphones9 internet9 client9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
mobile 23
avec 17
vous 16
offres 15
votre 12
mois 11
sport 9
téléphones 9
internet 9
client 9
Google Preview Your look like this in google search result
SFR | TÉLÉPHONE, FORFAIT MOBILE, INTERNET + FIBRE, SPORT, PL
https://www.sfr.fr
Découvrez les offres Mobile, TV, Internet et Fibre de SFR. Choisissez le forfait qui répond à vos besoins et retrouvez aussi le meilleur des contenus
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 1970-01-01 / 51 years
Create on: 1996-07-22 / 24 years
Expires on: 2019-11-18 / 12 months 13 days

Société Française du Radiotéléphone - SFR Société Française du Radiotéléphone - SFR Société Française du Radiotéléphone - SFR Société Française du Radiotéléphone - SFR Société Française du Radiotéléphone - SFR ,FR FR FR FR
Registrar Email: [email protected]
Registrar Address: 1, square Bela Bartok 75015 PARIS 1, square Bela Bartok 75015 Paris SOCIETE FRANCAISE DU RADIOTELEPHONE - SFR 42, avenue de Friedland 75008 Paris 1, square Bela Bartok 75015 Paris ,

Nameservers
ns1pub.sfr.fr
[92.90.26.129]
ns2pub.sfr.fr
[92.90.26.145]
Page Size Code & Text Ratio
Document Size: ~124.39 KB
Code Size: ~41.58 KB
Text Size: ~82.81 KB Ratio: 66.57%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 679 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 27 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,882 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 25 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 764 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 94 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 94 requests • 1,882 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 83 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Minify CSS Potential savings of 10 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 62 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 721 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Server response times are low (TTFB) Root document took 520 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 47 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 5 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Mobile

Mobile Screenshot
Keep request counts low and transfer sizes small 96 requests • 2,363 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 85 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 390 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 9.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Estimated Input Latency 90 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
First Contentful Paint (3G) 7860 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Minify CSS Potential savings of 10 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 77% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 80.69% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 62 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity
Serve images in next-gen formats Potential savings of 1,232 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce server response times (TTFB) Root document took 2,100 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,590 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 37 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 5 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Total Blocking Time 580 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 1,410 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Server Backend Latencies 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Properly size images Potential savings of 3 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 9.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 2,363 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.8 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 25 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoids an excessive DOM size 764 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 94 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 5.8 s
First Meaningful Paint measures when the primary content of a page is visible

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Wed, 27 Nov 2019 09:33:35 GMT
Server: Apache-Coyote/rtm-sfrfr13
Pragma: no-cache
Cache-Control: private
Expires: Wed, 31 Dec 1969 23:59:59 GMT
Content-Type: text/html;charset=UTF-8
Transfer-Encoding: chunked
Via: 1.1 www.sfr.fr
Via: http2
Set-Cookie: ROUTEID=.rtm-sfrfr13; path=/
Connection: close
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome