Free.fr - SEO Checker - Website Review

Your Website Score is

Similar Ranking

IDPAY | آیدی پی

idpay.ir

KÊNH THÔNG TIN KINH TẾ - TÀI CHÍNH VIỆT NAM

cafef.vn

FREE CLIP ART - CLIP ART COLLECTION - DOWNLOAD CLIPART ON CLIPART LIBRARY

clipart-library.com

MUBI: WATCH AND DISCOVER MOVIES

mubi.com

SIMPLENOTE

simplenote.com

МВД РОССИИ

xn--b1aew.xn--p1ai

سینماتیکت بزرگترین مرجع فروش بلیت سینما

cinematicket.org

Latest Sites

INVITATION TO REGISTER

home.takepocket.com

GOLIKE

tiktok.golike.one

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

41 free.fr Last Updated: 1 year

Success 62% of passed verification steps

Warning 23% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 38%

Best Practices Desktop Score 92%

SEO Desktop Score 91%

Progressive Web App Desktop Score 35%

Performance Mobile Score 22%

Best Practices Mobile Score 92%

SEO Mobile Score 84%

Progressive Web App Mobile Score 37%

Page Authority Authority 53%

Domain Authority Domain Authority 54%

Moz Rank 5.3/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 4 Characters

FREE

Meta Description 156 Characters

Découvrez les nouvelles offres Freebox One et Freebox Delta, disponibles dès maintenant. Internet ADSL2+, VDSL 2 ou FIBRE optique, Téléphonie, Télévision...

Effective URL 38 Characters

https://www.free.fr/freebox/index.html

Excerpt Page content

FreeFreeboxMobileBoutiquesWebmailAssistanceEspace AbonnéFreeboxFreebox DeltaL'offre Freebox DeltaSon DevialetNetflixAmazon PrimeTV by CANALFreebox TVAssistant vocalMaison connectéePack sécuritéCafeyn by LeKioskYoubooxFreebox Delta SL'offre Freebox De...

Keywords Cloud Density

freebox135 free49 delta43 pour40 offre35 mois32 avec32 fibre27 forfait27 vous26

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
freebox	135
free	49
delta	43
pour	40
offre	35
mois	32
avec	32
fibre	27
forfait	27
vous	26

Google Preview Your look like this in google search result

FREE

https://www.free.fr/freebox/index.html

Découvrez les nouvelles offres Freebox One et Freebox Delta, disponibles dès maintenant. Internet ADSL2+, VDSL 2 ou FIBRE optique, Téléphonie, Télévis

Robots.txt File Detected

http://free.fr/robots.txt

Sitemap.xml File Detected

http://free.fr/sitemap.xml

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: 1999-03-15 / 22 years

Expires on: 2020-12-23 / 1 months 6 days

ONLINE SAS ONLINE SAS ONLINE SAS ONLINE SAS ONLINE SAS ,FR FR FR FR

Registrar Email: [email protected]

Registrar Address: 8 Rue de la Ville l'Evêque 75008 PARIS 16 rue de la ville l'Eveque 75008 Paris 16 rue de la ville l'Eveque 75008 Paris 16 rue de la ville l'Eveque 75008 Paris ,

Nameservers

freens1-g20.free.fr

[212.27.60.19]

freens2-g20.free.fr

[212.27.60.20]

Page Size Code & Text Ratio

Document Size: ~232.42 KB

Code Size: ~120.33 KB

Text Size: ~112.08 KB Ratio: 48.23%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Properly size images Potential savings of 390 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 6.7 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 4.2 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).

Avoid enormous network payloads Total size was 3,713 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 5.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 0.7 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 11 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

Avoid an excessive DOM size 3,590 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)

First Meaningful Paint 2.0 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 127 requests • 3,713 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 105 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 1,550 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 6.3 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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 25.8 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 850 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

Serve images in next-gen formats Potential savings of 785 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 570 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 140 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 433 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 1,240 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 3.7 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,379 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

Mobile

Document doesn't use legible font sizes 37.44% 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

Serve images in next-gen formats Potential savings of 751 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 320 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 360 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 433 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 3,890 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 12.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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

Defer offscreen images Potential savings of 1,270 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 18.1 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 8.1 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).

Avoid enormous network payloads Total size was 3,615 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 18.3 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 2.5 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 11 chains found

Avoid an excessive DOM size 2,797 elements

First Meaningful Paint 8.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 115 requests • 3,615 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 93 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 5,060 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 23.8 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

Page load is not fast enough on mobile networks Interactive at 23.8 s

A fast page load over a cellular network ensures a good mobile user experience

First Contentful Paint (3G) 4980 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 3,660 ms

Tap targets are not sized appropriately 98% 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

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
Server: nginx
Date: Tue, 26 Nov 2019 06:20:12 GMT
Content-Type: text/html
Last-Modified: Wed, 20 Nov 2019 11:09:32 GMT
Connection: keep-alive
Vary: Accept-Encoding
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	free.fr	212.27.48.10	IN	7123
NS	free.fr	freens2-g20.free.fr	IN	21599
NS	free.fr	freens1-g20.free.fr	IN	21599
MX	free.fr	mx1.free.fr	IN	21599
MX	free.fr	mx2.free.fr	IN	21599
TXT	free.fr	google-site-verification=t11beEEtTGbjTRaHIR3ZAde9bcpIueH4i3Qn0orBExQ	IN	21599
AAAA	free.fr	2a01:e0c:1::1	IN	7123

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

41 free.fr Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Nginx

Piwik

React

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments