Francetvinfo.Fr francetvinfo.fr

france3-Regions.Blog.Francetvinfo.Fr

france3-regions.blog.francetvinfo.fr receives about 1,170,352 unique visitors and 1,638,493 (1.40 per visitor) page views per day which should earn about $7,519.65/day from advertising revenue. Estimated site value is $5,504,559.42. According to Alexa Traffic Rank france3-regions.blog.francetvinfo.fr is ranked number 3,286 in the world and 0.0258% of global Internet users visit it. Site is hosted in Los Angeles, CA, 90001, Netherlands and links to network IP address 23.209.102.57. This server doesn't support HTTPS and doesn't support HTTP/2.

About - france3-regions.blog.francetvinfo.fr

Plateforme de blogs - Index
Edit Site Info

Technologies used on Website

Analytics
Google Analytics
JavaScript Frameworks
Prototype
RequireJS
CMS
WordPress
Blogs
WordPress
Programming Languages
PHP
Databases
MySQL

france3-regions.blog.francetvinfo.fr Profile

Title: Plateforme de blogs - Index
Keywords: plateforme de blogs - index
Last update was 110 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with francetvinfo.fr in any way. Only publicly available statistics data are displayed.

How popular is france3-regions.blog.francetvinfo.fr?

1.2M daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,170,352
Monthly Unique Visitors:
28,088,448
Pages per Visit:
1.40
Daily Pageviews:
1,638,493
Alexa Rank:
3,286 visit alexa
Alexa Reach:
0.0258%   (of global internet users)
Avg. visit duration:
03:10
Bounce rate:
63.37%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
31.25%
Referral:
3.27%
Search:
45.82%
Social:
12.10%
Paid:
0.22%

Visitors by country

Users%Pageviews%Rank
France 73.8%68.6%80
United States 4.7%7.7%10001
Luxembourg 2.3%3.4%133
Switzerland 1.8%1.8%1164
Brazil 1.5%2.1%7197
Canada 1.5%1.9%4074
Belgium 1.4%1.1%1242
Martinique 1.4%2.8%10
Algeria 0.8%0.7%1869
Reunion 0.7%1.0%26
Morocco 0.6%0.7%1476
Tunisia 0.6%0.5%1101
Burkina Faso 0.6%0.5%177
Madagascar 0.5%0.4%286

Where do visitors go on this site?

Reach%Pageviews%PerUser
francetvinfo.fr
60.63%63.99%1.5
france3-regions.francetvinfo.fr
31.25%24.96%1.1
la1ere.francetvinfo.fr
6.56%7.74%1.7
mobile.francetvinfo.fr
1.87%1.32%1
sport.francetvinfo.fr
1.51%1.08%1
OTHER
0%0.92%0

Competitive Data

SEMrush
Domain:
  france3-regions.blog.francetvinfo.fr
Rank:
(Rank based on keywords, cost and organic traffic)
  23,164
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  247,923
Organic Traffic:
(Number of visitors coming from top 20 search results)
  100,349
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $11,109.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  10
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  388
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $96.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is france3-regions.blog.francetvinfo.fr?

Facebook:
  5
Google +:
  2
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
francetvinfo.fr
Last Change Time:
(The last time that the site changed status.)
2019-08-16 08:56:06
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing


Mobile summary

Last Change Time:
(The last time that the site changed status.)
2019-08-16 08:56:06
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing

+ Abusive Experience Report

Root domain:
francetvinfo.fr
Last Change Time:
(The last time that the site changed status.)
2019-08-16 08:56:06
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Passing

+ How much france3-regions.blog.francetvinfo.fr can earn?

Daily Revenue:
$7,519.65
Monthly Revenue:
$225,589.50
Yearly Revenue:
$2,744,672.25
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
France 1,124,006$5,282.83
United States 126,164$1,447.10
Canada 31,131$218.23
Switzerland 29,493$179.02
Luxembourg 55,709$125.90
Belgium 18,023$88.86
Martinique 45,878$61.02
Brazil 34,408$60.90
Reunion 16,385$14.75
Algeria 11,469$10.32
Madagascar 6,554$9.90
Tunisia 8,192$7.54
Morocco 11,469$6.65
Burkina Faso 8,192$6.64

How much money do france3-regions.blog.francetvinfo.fr lose due to Adblock?

Daily Revenue Loss:
$967.27
Monthly Revenue Loss:
$29,018.09
Yearly Revenue Loss:
$353,053.46
Daily Pageviews Blocked:
176,826
Monthly Pageviews Blocked:
5,304,785
Yearly Pageviews Blocked:
64,541,550
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
France 123,641$581.11
United States 22,710$260.48
Canada 7,783$54.56
Switzerland 5,309$32.22
Luxembourg 8,356$18.89
Belgium 2,163$10.66
Martinique 3,211$4.27
Brazil 2,065$3.65
Algeria 573$0.52
Reunion 328$0.29
Madagascar 131$0.20
Tunisia 164$0.15
Morocco 229$0.13
Burkina Faso 164$0.13

How much is france3-regions.blog.francetvinfo.fr worth?

Website Value:
$5,504,559.42

+ Where is france3-regions.blog.francetvinfo.fr hosted?

Server IP:
23.209.102.57
ASN:
AS35994 
ISP:
Akamai Technologies, Inc. 
Server Location:
Los Angeles
CA
90001
Netherlands, NL
 

Other sites hosted on 23.209.102.57

There are no other sites hosted on this IP

+ How fast does france3-regions.blog.francetvinfo.fr load?

Average Load Time:
(1047 ms) 77 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

95
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)2.6s 22% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 22% 57% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 57% 19% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 19%
First Input Delay (FID)91ms 95% of loads for this page have a fast (<100ms) First Input Delay (FID) 95% 3% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)2.6s 22% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 22% 57% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 57% 19% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 19%
First Input Delay (FID)91ms 95% of loads for this page have a fast (<100ms) First Input Delay (FID) 95% 3% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Lab Data

First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
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. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 8 requests • 46 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
846 KB
Script
328 KB
Document
116 KB
Stylesheet
11 KB
Image
11 KB
Other
20 KB
Media
00 KB
Font
00 KB
Third-party
529 KB
Eliminate render-blocking resources - Potential savings of 220 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
1 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://france3-regions.blog.francetvinfo.fr/
0 ms35 ms0 KB0 KB301
https://france3-regions.blog.francetvinfo.fr/
35 ms1134 ms16 KB49 KB200text/htmlDocument
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
1148 ms2054 ms1 KB0 KB200text/cssStylesheet
https://ssl.google-analytics.com/ga.js
2057 ms2063 ms17 KB45 KB200text/javascriptScript
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1799412695&utmhn=france3-regions.blog.francetvinfo.fr&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Plateforme%20de%20blogs%20-%20Index&utmhid=583080156&utmr=-&utmp=%2F&utmht=1576316058583&utmac=UA-30735148-3&utmcc=__utma%3D73024320.1095765351.1576316059.1576316059.1576316059.1%3B%2B__utmz%3D73024320.1576316059.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=575305105&utmredir=1&utmu=qBAAAAAAAAAAAAAAAAAAAAAE~
2139 ms2145 ms1 KB0 KB200image/gifImage
https://js-agent.newrelic.com/nr-1153.min.js
2148 ms2177 ms10 KB26 KB200application/javascriptScript
https://bam.nr-data.net/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=2188&ref=https://france3-regions.blog.francetvinfo.fr/&ap=51&be=1153&fe=2149&dc=2089&af=err,xhr,stn,ins&perf=%7B%22timing%22:%7B%22of%22:1576316056456,%22n%22:0,%22f%22:37,%22dn%22:37,%22dne%22:37,%22c%22:37,%22ce%22:37,%22rq%22:37,%22rp%22:1136,%22rpe%22:1136,%22dl%22:1144,%22di%22:2089,%22ds%22:2089,%22de%22:2090,%22dc%22:2149,%22l%22:2149,%22le%22:2150%7D,%22navigation%22:%7B%7D%7D&fp=2124&fcp=2124&at=HhZSRw9NRE8%3D&jsonp=NREUM.setToken
2188 ms2222 ms0 KB0 KB200text/javascriptScript
https://bam.nr-data.net/resources/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=2228&ref=https://france3-regions.blog.francetvinfo.fr/&st=1576316056456&at=HhZSRw9NRE8%3D
2229 ms2263 ms0 KB0 KB200text/plainXHR
Uses efficient cache policy on static assets - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://ssl.google-analytics.com/ga.js
7200000 ms17 KB
https://js-agent.newrelic.com/nr-1153.min.js
7200000 ms10 KB
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
86400000 ms1 KB
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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
18 KB0 ms
11 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1163 ms
7 ms
1174 ms
12 ms
2085 ms
28 ms
2119 ms
46 ms
2204 ms
10 ms
2249 ms
7 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
56 ms3 ms1 ms
Avoids enormous network payloads - Total size was 46 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://ssl.google-analytics.com/ga.js
17 KB
https://france3-regions.blog.francetvinfo.fr/
16 KB
https://js-agent.newrelic.com/nr-1153.min.js
10 KB
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
1 KB
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1799412695&utmhn=france3-regions.blog.francetvinfo.fr&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Plateforme%20de%20blogs%20-%20Index&utmhid=583080156&utmr=-&utmp=%2F&utmht=1576316058583&utmac=UA-30735148-3&utmcc=__utma%3D73024320.1095765351.1576316059.1576316059.1576316059.1%3B%2B__utmz%3D73024320.1576316059.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=575305105&utmredir=1&utmu=qBAAAAAAAAAAAAAAAAAAAAAE~
1 KB
http://france3-regions.blog.francetvinfo.fr/
0 KB
https://bam.nr-data.net/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=2188&ref=https://france3-regions.blog.francetvinfo.fr/&ap=51&be=1153&fe=2149&dc=2089&af=err,xhr,stn,ins&perf=%7B%22timing%22:%7B%22of%22:1576316056456,%22n%22:0,%22f%22:37,%22dn%22:37,%22dne%22:37,%22c%22:37,%22ce%22:37,%22rq%22:37,%22rp%22:1136,%22rpe%22:1136,%22dl%22:1144,%22di%22:2089,%22ds%22:2089,%22de%22:2090,%22dc%22:2149,%22l%22:2149,%22le%22:2150%7D,%22navigation%22:%7B%7D%7D&fp=2124&fcp=2124&at=HhZSRw9NRE8%3D&jsonp=NREUM.setToken
0 KB
https://bam.nr-data.net/resources/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=2228&ref=https://france3-regions.blog.francetvinfo.fr/&st=1576316056456&at=HhZSRw9NRE8%3D
0 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
75 ms
Style & Layout
24 ms
Other
21 ms
Script Parsing & Compilation
8 ms
Rendering
4 ms
Parse HTML & CSS
3 ms
Garbage Collection
0 ms
Avoids an excessive DOM size - 368 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). Learn more.

Statistic
ElementValue
Total DOM Elements
368
Maximum DOM Depth
4
Maximum Child Elements
100
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://france3-regions.blog.francetvinfo.fr/)
0
https://france3-regions.blog.francetvinfo.fr/
190
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 1,100 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

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

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. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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. Learn more.

Serve images in next-gen formats
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. Learn more.

Avoid chaining critical requests - 1 chain 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

94
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)2.2s 22% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 21% 66% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 66% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
First Input Delay (FID)277ms 89% of loads for this page have a fast (<100ms) First Input Delay (FID) 89% 6% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 6% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)2.2s 21% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 21% 66% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 66% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
First Input Delay (FID)277ms 95% of loads for this page have a fast (<100ms) First Input Delay (FID) 89% 6% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 6% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%

Lab Data

Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 3990 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
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. Learn more.
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 46 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://ssl.google-analytics.com/ga.js
17 KB
https://france3-regions.blog.francetvinfo.fr/
16 KB
https://js-agent.newrelic.com/nr-1153.min.js
10 KB
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
1 KB
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=46050066&utmhn=france3-regions.blog.francetvinfo.fr&utmcs=UTF-8&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Plateforme%20de%20blogs%20-%20Index&utmhid=1150228717&utmr=-&utmp=%2F&utmht=1576316051886&utmac=UA-30735148-3&utmcc=__utma%3D73024320.668619730.1576316052.1576316052.1576316052.1%3B%2B__utmz%3D73024320.1576316052.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1324337986&utmredir=1&utmu=qBAAAAAAAAAAAAAAAAAAAAAE~
1 KB
http://france3-regions.blog.francetvinfo.fr/
0 KB
https://bam.nr-data.net/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=1985&ref=https://france3-regions.blog.francetvinfo.fr/&ap=110&be=1390&fe=1940&dc=1889&af=err,xhr,stn,ins&perf=%7B%22timing%22:%7B%22of%22:1576316049965,%22n%22:0,%22f%22:200,%22dn%22:200,%22dne%22:200,%22c%22:200,%22ce%22:200,%22rq%22:200,%22rp%22:1372,%22rpe%22:1372,%22dl%22:1379,%22di%22:1888,%22ds%22:1888,%22de%22:1889,%22dc%22:1939,%22l%22:1939,%22le%22:1940%7D,%22navigation%22:%7B%7D%7D&fp=1910&fcp=1910&at=HhZSRw9NRE8%3D&jsonp=NREUM.setToken
0 KB
https://bam.nr-data.net/resources/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=2024&ref=https://france3-regions.blog.francetvinfo.fr/&st=1576316049965&at=HhZSRw9NRE8%3D
0 KB
Minimizes main-thread work - 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
267 ms
Style & Layout
107 ms
Other
98 ms
Script Parsing & Compilation
36 ms
Rendering
21 ms
Parse HTML & CSS
15 ms
Avoids an excessive DOM size - 368 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). Learn more.

Statistic
ElementValue
Total DOM Elements
368
Maximum DOM Depth
4
Maximum Child Elements
100
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://france3-regions.blog.francetvinfo.fr/)
0
https://france3-regions.blog.francetvinfo.fr/
630
Keep request counts low and transfer sizes small - 8 requests • 46 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
846 KB
Script
328 KB
Document
116 KB
Stylesheet
11 KB
Image
11 KB
Other
20 KB
Media
00 KB
Font
00 KB
Third-party
529 KB
Eliminate render-blocking resources - Potential savings of 720 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
1 KB780
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://france3-regions.blog.francetvinfo.fr/
0 ms199 ms0 KB0 KB301
https://france3-regions.blog.francetvinfo.fr/
200 ms1371 ms16 KB49 KB200text/htmlDocument
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
1387 ms1848 ms1 KB0 KB200text/cssStylesheet
https://ssl.google-analytics.com/ga.js
1852 ms1857 ms17 KB45 KB200text/javascriptScript
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=46050066&utmhn=france3-regions.blog.francetvinfo.fr&utmcs=UTF-8&utmsr=412x660&utmvp=980x1569&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Plateforme%20de%20blogs%20-%20Index&utmhid=1150228717&utmr=-&utmp=%2F&utmht=1576316051886&utmac=UA-30735148-3&utmcc=__utma%3D73024320.668619730.1576316052.1576316052.1576316052.1%3B%2B__utmz%3D73024320.1576316052.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1324337986&utmredir=1&utmu=qBAAAAAAAAAAAAAAAAAAAAAE~
1930 ms1936 ms1 KB0 KB200image/gifImage
https://js-agent.newrelic.com/nr-1153.min.js
1939 ms1974 ms10 KB26 KB200application/javascriptScript
https://bam.nr-data.net/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=1985&ref=https://france3-regions.blog.francetvinfo.fr/&ap=110&be=1390&fe=1940&dc=1889&af=err,xhr,stn,ins&perf=%7B%22timing%22:%7B%22of%22:1576316049965,%22n%22:0,%22f%22:200,%22dn%22:200,%22dne%22:200,%22c%22:200,%22ce%22:200,%22rq%22:200,%22rp%22:1372,%22rpe%22:1372,%22dl%22:1379,%22di%22:1888,%22ds%22:1888,%22de%22:1889,%22dc%22:1939,%22l%22:1939,%22le%22:1940%7D,%22navigation%22:%7B%7D%7D&fp=1910&fcp=1910&at=HhZSRw9NRE8%3D&jsonp=NREUM.setToken
1986 ms2019 ms0 KB0 KB200text/javascriptScript
https://bam.nr-data.net/resources/1/df5532f36e?a=31798454&v=1153.61ee9ba&to=MlFRMUdXV0FSUERQXAsbZhdcGVBcV1ZIF0MNRA%3D%3D&rst=2024&ref=https://france3-regions.blog.francetvinfo.fr/&st=1576316049965&at=HhZSRw9NRE8%3D
2026 ms2059 ms0 KB0 KB200text/plainXHR
Uses efficient cache policy on static assets - 3 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://ssl.google-analytics.com/ga.js
7200000 ms17 KB
https://js-agent.newrelic.com/nr-1153.min.js
7200000 ms10 KB
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css
86400000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 80 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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
18 KB80 ms
11 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1405 ms
9 ms
1418 ms
14 ms
1886 ms
33 ms
1926 ms
36 ms
2008 ms
11 ms
2052 ms
8 ms
JavaScript execution time - 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
258 ms12 ms5 ms
https://ssl.google-analytics.com/ga.js
143 ms134 ms8 ms
https://france3-regions.blog.francetvinfo.fr/
75 ms63 ms12 ms
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. Learn more.

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

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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. Learn more.

Serve images in next-gen formats
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. Learn more.

Avoid chaining critical requests - 1 chain 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 1,170 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Les autres pla…rme de blogs : and 2 others render only 8 pixels tall (20 CSS pixels) .
14/12/2019 10:55:46 : and 99 others render only 5 pixels tall (13 CSS pixels) .
Du journalisme…constructives and 178 others render only 5 pixels tall (13 CSS pixels) .

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://www.me…itannique.html">Liens vagabond…ue britannique</a> and 150 others are close to other tap targets .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://js-agent.newrelic.com/nr-1153.min.js (2 hours)
https://ssl.google-***ytics.com/ga.js (2 hours)
https://blog.francetvinfo.fr/wp-content/plugins/ftvi-index-page/public/assets/css/public.css (24 hours)
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does france3-regions.blog.francetvinfo.fr use compression?

france3-regions.blog.francetvinfo.fr use gzip compression.
Original size: 48.89 KB
Compressed size: 15.61 KB
File reduced by: 33.28 KB (68%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  68
Vendor reliability:
  68
Privacy:
  68
Child safety:
  86

+ SSL Checker - SSL Certificate Verify

france3-regions.blog.francetvinfo.fr does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

france3-regions.blog.francetvinfo.fr does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: AkamaiGHost
Content-Length: 0
Location: https://france3-regions.blog.francetvinfo.fr/
Date: Sat, 14 Dec 2019 09:33:59 GMT
Connection: keep-alive
X-Ak-mobile-redirect: yes

HTTP/1.1 200 OK
Content-Encoding: gzip
Expires: Sat, 14 Dec 2019 09:25:57 GMT
Strict-Transport-Security: max-age=300
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode = block
Content-Length: 15981
Content-Type: text/html; charset=UTF-8
Cache-Control: public, max-age=900
Accept-Ranges: bytes
Date: Sat, 14 Dec 2019 09:33:59 GMT
Connection: keep-alive
Vary: Accept-Encoding
X-Ak-mobile-redirect: yes

+ DNS Lookup

Type Ip Target TTL
CNAME 2-01-55a9-00b6.cdx.cedexis.net 277

+ Whois Lookup

Domain Created:
2008-08-25
Domain Age:
11 years 3 months 20 days  
WhoIs:
 

whois lookup at whois.nic.fr...
%%

domain: francetvinfo.fr
status: ACTIVE
hold: NO
holder-c: FTS84-FRNIC
admin-c: BUGG1415-FRNIC
tech-c: IC3447-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL86234-FRNIC
registrar: ASCIO TECHNOLOGIES Inc.
anniversary: 23/07
created: 25/08/2008
last-update: 16/04/2014
source: FRNIC

ns-list: NSL86234-FRNIC
nserver: ns-856.awsdns-43.net
nserver: ns-1505.awsdns-60.org
nserver: ns-1718.awsdns-22.co.uk
nserver: ns-85.awsdns-10.com
source: FRNIC

registrar: ASCIO TECHNOLOGIES Inc.
type: Isp Option 1
address: Islands Brygge 55
address: DK-2300 COPENHAGUE S
country: DK
phone: +45 33 88 61 00
fax-no: +45 33 88 61 01
e-mail: email
website: http://www.ascio.com
anonymous: NO
registered: 18/01/2001
source: FRNIC

nic-hdl: FTS84-FRNIC
type: ORGANIZATION
contact: France Televisions S.A.
address: France Televisions
address: 7, esplanade Henri de France
address: 75015 Paris
country: FR
phone: +33 1 56 22 51 35
fax-no: +33 1 56 22 35 74
e-mail: email
registrar: ASCIO TECHNOLOGIES Inc.
changed: 03/09/2012 email
anonymous: NO
obsoleted: NO
eligstatus: ok
eligsource: REGISTRY
eligdate: 18/02/2014 15:54:48
reachmedia: phone
reachstatus: ok
reachsource: REGISTRY
reachdate: 18/02/2014 15:54:48
source: FRNIC

nic-hdl: BUGG1415-FRNIC
type: PERSON
contact: - -
address: France Televisions
address: 7, esplanade Henri de France
address: 75015 Paris
country: FR
phone: +33 1 56 22 51 35
fax-no: +33 1 56 22 35 74
e-mail: email
registrar: ASCIO TECHNOLOGIES Inc.
changed: 03/09/2012 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: IC3447-FRNIC
type: PERSON
contact: Indom Contact
address: 124-126, rue de Provence
address: 75008 Paris
country: FR
phone: +33 1 76 70 05 67
fax-no: +33 1 48 01 67 73
e-mail: email
registrar: ASCIO TECHNOLOGIES Inc.
changed: 03/09/2012 email
anonymous: NO
obsoleted: NO
source: FRNIC
Last update was 110 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with francetvinfo.fr in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

d-logika.com
57 secs
esports.nl
1 min
nnxnn.com
1 min
fullandroidwatch.com
2 mins
openini.by
2 mins
naijajeodax.com
3 mins
mybenihana.com
4 mins
zains.net
5 mins
whatfinger.com
5 mins
tumplr.com
6 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
france3-regions.blog.francetvinfo.fr widget