3.4 sec in total
192 ms
3 sec
276 ms
Click here to check amazing R E F content for France. Otherwise, check out these important facts you probably never knew about r-e-f.org
Site officiel du Réseau des Émetteurs Français
Visit r-e-f.orgWe analyzed R-e-f.org page load time and found that the first response time was 192 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
r-e-f.org performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value6.4 s
9/100
25%
Value7.2 s
30/100
10%
Value20 ms
100/100
30%
Value0.002
100/100
15%
Value5.7 s
69/100
10%
192 ms
1133 ms
159 ms
160 ms
160 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 87% of them (54 requests) were addressed to the original R-e-f.org, 5% (3 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain R-e-f.org.
Page size can be reduced by 215.0 kB (42%)
510.8 kB
295.8 kB
In fact, the total size of R-e-f.org main page is 510.8 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. 30% of websites need less resources to load. Images take 266.3 kB which makes up the majority of the site volume.
Potential reduce by 45.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.5 kB or 79% of the original size.
Potential reduce by 34.5 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. Obviously, R E F needs image optimization as it can save up to 34.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 93.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 93.3 kB or 69% of the original size.
Potential reduce by 41.7 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. R-e-f.org needs all CSS files to be minified and compressed as it can save up to 41.7 kB or 82% of the original size.
Number of requests can be reduced by 42 (70%)
60
18
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of R E F. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
r-e-f.org
192 ms
www.r-e-f.org
1133 ms
jceutilities.css
159 ms
style.css
160 ms
modstyle.css
160 ms
mediaobject-150.js
175 ms
mootools.js
385 ms
jceutilities.js
402 ms
caption.js
329 ms
phocagalleryslideshow.js
339 ms
swfobject.js
330 ms
system.css
368 ms
general.css
491 ms
template.css
586 ms
ja.script.js
496 ms
ja.rightcol.js
539 ms
menu.css
544 ms
ja-sosdmenu.css
548 ms
ja.cssmenu.js
646 ms
style.css
666 ms
style.css
740 ms
urchin.js
23 ms
user-increase.png
179 ms
user-reset.png
180 ms
user-decrease.png
214 ms
f8ref.jpg
559 ms
get_flash_player.gif
62 ms
bullet.gif
100 ms
test.png
148 ms
header8.jpg
259 ms
header-mask.png
207 ms
logo.png
233 ms
arrow2.png
252 ms
cw-bg1.gif
244 ms
cw-bg2.gif
319 ms
c-bg1.gif
384 ms
c-bg2.gif
404 ms
hdot.gif
405 ms
station.jpg
516 ms
adhesion_2016.jpg
530 ms
arrow.png
502 ms
tabheaderblue.jpg
559 ms
livemarks.png
561 ms
iaru.gif
584 ms
bfra-logo1.jpeg
752 ms
logo_anfr.png
698 ms
Logo_ITU-1.JPG
692 ms
but-css.gif
717 ms
but-xhtml10.gif
720 ms
widgets.js
18 ms
b-br.gif
717 ms
b-bl.gif
822 ms
b-tr.gif
821 ms
b-tl.gif
831 ms
grad1.gif
832 ms
hdot2.gif
825 ms
grad3.gif
849 ms
vdot.gif
952 ms
__utm.gif
21 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
35 ms
follow_button.6a78875565a912489e9aef879c881358.fr.html
21 ms
jot
114 ms
r-e-f.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
r-e-f.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
r-e-f.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R-e-f.org can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that R-e-f.org 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.
r-e-f.org
Open Graph description is not detected on the main page of R E F. 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: