Tools & Wizards About Us
freepost.fr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

freepost.fr

Félicitations ! Votre domaine a bien été créé chez OVHcloud !

Page Load Speed

1.4 sec in total

First Response

275 ms

Resources Loaded

1 sec

Page Rendered

167 ms

freepost.fr screenshot

About Website

Click here to check amazing Freepost content. Otherwise, check out these important facts you probably never knew about freepost.fr

OVHcloud accompagne votre évolution grâce au meilleur des infrastructures web : hébergement, nom de domaine, serveur dédié, CDN, Cloud, Big Data, ...

Visit freepost.fr

Key Findings

We analyzed Freepost.fr page load time and found that the first response time was 275 ms and then it took 1.2 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.

Performance Metrics

freepost.fr performance score

0

Network Requests Diagram

freepost.fr

275 ms

reset.css

81 ms

styles.css

161 ms

widgets.js

21 ms

plusone.js

89 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 50% of them (28 requests) were addressed to the original Freepost.fr, 16% (9 requests) were made to Static.xx.fbcdn.net and 14% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (524 ms) belongs to the original domain Freepost.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.2 kB (21%)

Content Size

143.9 kB

After Optimization

113.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Freepost.fr main page is 143.9 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 72.7 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 10.0 kB

  • Original 14.3 kB
  • After minification 13.3 kB
  • After compression 4.3 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 10.0 kB or 70% of the original size.

Image Optimization

-11%

Potential reduce by 7.8 kB

  • Original 72.7 kB
  • After minification 64.9 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, Freepost needs image optimization as it can save up to 7.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 6.1 kB

  • Original 48.6 kB
  • After minification 48.6 kB
  • After compression 42.5 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 6.1 kB or 13% of the original size.

CSS Optimization

-76%

Potential reduce by 6.3 kB

  • Original 8.3 kB
  • After minification 7.0 kB
  • After compression 2.0 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. Freepost.fr needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (70%)

Requests Now

54

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freepost. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

freepost.fr

freepost.fr

275 ms

reset.css

reset.css

81 ms

styles.css

styles.css

161 ms

widgets.js

widgets.js

21 ms

plusone.js

plusone.js

89 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

analytics.js

analytics.js

25 ms

like.php

like.php

96 ms

ga.js

ga.js

14 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

12 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

79 ms

fastbutton

fastbutton

114 ms

header-background.gif

header-background.gif

118 ms

footer-background.gif

footer-background.gif

117 ms

header.jpg

header.jpg

311 ms

logo-librestamp.png

logo-librestamp.png

262 ms

navigation-background.jpg

navigation-background.jpg

259 ms

separateur.gif

separateur.gif

258 ms

navigation-select.gif

navigation-select.gif

258 ms

loggin-background.jpg

loggin-background.jpg

261 ms

form-field-background.gif

form-field-background.gif

297 ms

form-btn-ok.gif

form-btn-ok.gif

297 ms

inscription.jpg

inscription.jpg

369 ms

right-column-ombre.gif

right-column-ombre.gif

345 ms

icon-facebook.gif

icon-facebook.gif

345 ms

icon-favorites.gif

icon-favorites.gif

377 ms

icon-digg.gif

icon-digg.gif

378 ms

icon-delicious.gif

icon-delicious.gif

385 ms

icon-blogger.gif

icon-blogger.gif

424 ms

icon-google.gif

icon-google.gif

422 ms

icon-aim.gif

icon-aim.gif

446 ms

icon-linkedin.gif

icon-linkedin.gif

453 ms

icon-feedburner.gif

icon-feedburner.gif

458 ms

icon-twitter.gif

icon-twitter.gif

462 ms

librestamp-icon-money.jpg

librestamp-icon-money.jpg

499 ms

librestamp-icon-time.jpg

librestamp-icon-time.jpg

502 ms

footer.jpg

footer.jpg

524 ms

__utm.gif

__utm.gif

34 ms

f1b0EAiQ-wg.css

f1b0EAiQ-wg.css

90 ms

RJJsRWCWmtW.css

RJJsRWCWmtW.css

86 ms

AdP_CKHZFBh.css

AdP_CKHZFBh.css

88 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

93 ms

DFmZn3_ZO2h.js

DFmZn3_ZO2h.js

87 ms

mfqI3d6rUg1.js

mfqI3d6rUg1.js

113 ms

_Qp3v7kqEMi.js

_Qp3v7kqEMi.js

140 ms

postmessageRelay

postmessageRelay

166 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

50 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

84 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

59 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

156 ms

Bw8qRoQ9D-v.js

Bw8qRoQ9D-v.js

14 ms

4ylGxU24Rah.js

4ylGxU24Rah.js

19 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

37 ms

rpc:shindig_random.js

rpc:shindig_random.js

44 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

jot

jot

95 ms

SEO Factors

freepost.fr SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freepost.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 Freepost.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.

Social Sharing Optimization

freepost.fr

Open Graph description is not detected on the main page of Freepost. 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: