Tools & Wizards About Us
fr.nf screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

fr.nf

Nom de domaine Gratuit avec Azote.org et SANS PUBLICITE

Page Load Speed

1.9 sec in total

First Response

241 ms

Resources Loaded

1.5 sec

Page Rendered

99 ms

fr.nf screenshot

About Website

Click here to check amazing Fr content for France. Otherwise, check out these important facts you probably never knew about fr.nf

Nom de domaine gratuit sans publicité proposé par Azote.org. Extensions disponibles : .asso.st, .fr.cr, .fr.nf, .biz.st, .ze.cx, .xxl.st, .infos.st

Visit fr.nf

Key Findings

We analyzed Fr.nf page load time and found that the first response time was 241 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

fr.nf performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

www.azote.org

241 ms

www.azote.org

450 ms

style.css

82 ms

plusone.js

23 ms

facebook.png

178 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fr.nf, 22% (6 requests) were made to Apis.google.com and 7% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (474 ms) relates to the external source Azote.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.5 kB (11%)

Content Size

389.1 kB

After Optimization

346.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fr.nf main page is 389.1 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. Javascripts take 198.5 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 6.0 kB

  • Original 9.5 kB
  • After minification 9.1 kB
  • After compression 3.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 6.0 kB or 63% of the original size.

Image Optimization

-0%

Potential reduce by 92 B

  • Original 172.6 kB
  • After minification 172.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. Fr images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 29.5 kB

  • Original 198.5 kB
  • After minification 198.5 kB
  • After compression 169.0 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 29.5 kB or 15% of the original size.

CSS Optimization

-81%

Potential reduce by 6.8 kB

  • Original 8.5 kB
  • After minification 7.0 kB
  • After compression 1.6 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. Fr.nf needs all CSS files to be minified and compressed as it can save up to 6.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (57%)

Requests Now

23

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.azote.org

www.azote.org

241 ms

www.azote.org

www.azote.org

450 ms

style.css

style.css

82 ms

plusone.js

plusone.js

23 ms

facebook.png

facebook.png

178 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

ga.js

ga.js

45 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

27 ms

fastbutton

fastbutton

25 ms

bg.jpg

bg.jpg

153 ms

header.jpg

header.jpg

474 ms

separ.gif

separ.gif

235 ms

footer.jpg

footer.jpg

245 ms

fondmenu.png

fondmenu.png

247 ms

fondtitremenu.jpg

fondtitremenu.jpg

254 ms

puce.gif

puce.gif

260 ms

puce2.gif

puce2.gif

315 ms

style.css

style.css

326 ms

fondbtn.jpg

fondbtn.jpg

328 ms

checkedn.gif

checkedn.gif

338 ms

checked.gif

checked.gif

346 ms

postmessageRelay

postmessageRelay

92 ms

__utm.gif

__utm.gif

15 ms

developers.google.com

developers.google.com

290 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

20 ms

rpc:shindig_random.js

rpc:shindig_random.js

5 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

Accessibility Review

fr.nf accessibility score

55

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

fr.nf best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fr.nf SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fr.nf 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 Fr.nf main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fr.nf

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