4.4 sec in total
560 ms
3.3 sec
486 ms
Click here to check amazing Afnic content. Otherwise, check out these important facts you probably never knew about afnic.re
L'Afnic est le Registre Internet des noms de domaine en .fr, .re, .pm, .yt, .wf et .tf. / Solutions de Registre - AFNIC
Visit afnic.reWe analyzed Afnic.re page load time and found that the first response time was 560 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
afnic.re performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value9.9 s
0/100
25%
Value8.1 s
21/100
10%
Value1,220 ms
20/100
30%
Value0
100/100
15%
Value10.3 s
25/100
10%
560 ms
557 ms
177 ms
258 ms
262 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Afnic.re, 3% (2 requests) were made to Afnic.innocraft.cloud and 1% (1 request) were made to Tarteaucitron.io. The less responsive or slowest element that took the longest time to load (739 ms) relates to the external source Afnic.fr.
Page size can be reduced by 186.6 kB (28%)
676.4 kB
489.8 kB
In fact, the total size of Afnic.re main page is 676.4 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 305.9 kB which makes up the majority of the site volume.
Potential reduce by 100.7 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. This page needs HTML code to be minified as it can gain 18.5 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 100.7 kB or 85% of the original size.
Potential reduce by 62.3 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, Afnic needs image optimization as it can save up to 62.3 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 15.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. This website has mostly compressed JavaScripts.
Potential reduce by 8.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. Afnic.re has all CSS files already compressed.
Number of requests can be reduced by 47 (70%)
67
20
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Afnic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.afnic.fr
560 ms
load.js
557 ms
classic-themes.min.css
177 ms
dnd-upload-cf7.css
258 ms
styles.css
262 ms
cf7mls.css
263 ms
animate.min.css
268 ms
style.css
266 ms
bootstrap.min.css
376 ms
ctc-style.css
342 ms
all.min.css
353 ms
main.css
350 ms
style.css
358 ms
slick.css
358 ms
style.css
514 ms
language-cookie.js
437 ms
jquery.min.js
532 ms
jquery-migrate.min.js
449 ms
index.js
364 ms
index.js
387 ms
codedropz-uploader-min.js
443 ms
dnd-upload-cf7.js
455 ms
widget.module.min.js
458 ms
widget.polyfilled.min.js
551 ms
script.js
552 ms
cf7mls.js
552 ms
scripts.js
552 ms
comment-reply.min.js
553 ms
bootstrap.bundle.min.js
554 ms
main.js
576 ms
scripts.js
739 ms
slick.min.js
619 ms
smush-lazy-load.min.js
623 ms
wp-emoji-release.min.js
127 ms
flexvideo.css
109 ms
matomo.js
148 ms
GKzoFlNXIAAf_4n
139 ms
arrowselect-1.svg
135 ms
pastille-fr.png
137 ms
shapefr-multi.svg
132 ms
circle-shape.svg
132 ms
ressource-actualite.svg
137 ms
ressource-papier-expert.svg
182 ms
ressource-agenda.svg
186 ms
ressource-key-fact.svg
184 ms
ressource-observatoire.svg
187 ms
ressource-social_network.svg
189 ms
twitter-orange.svg
192 ms
arrowright-b.svg
232 ms
arrowtop-w.svg
267 ms
whois-shape.svg
221 ms
nav-1.svg
228 ms
email-w.svg
231 ms
fb-w.svg
237 ms
linkedin-w.svg
269 ms
twitter-w.svg
307 ms
insta-w.svg
308 ms
mastodon-w.svg
318 ms
Poppins-Regular.woff
403 ms
Poppins-Medium.woff
433 ms
Poppins-Bold.woff
453 ms
ZillaSlab-Regular.woff
480 ms
ZillaSlab-Bold.woff
566 ms
afnic-1.svg
383 ms
presentation-site-intro6-1.jpg
547 ms
play.svg
463 ms
pastille-fr.png
477 ms
Parc_actuel-FR.png
504 ms
header-news-caroline-duval-favre-293x160.jpg
538 ms
matomo.php
476 ms
configs.php
413 ms
header-blog-pharmaceutique-293x160.jpg
92 ms
tarteaucitron.fr.min.js
429 ms
afnic.re accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
afnic.re best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
afnic.re SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afnic.re 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 Afnic.re 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.
afnic.re
Open Graph data is detected on the main page of Afnic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: