Report Summary

  • 46

    Performance

    Renders faster than
    66% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

fdns.net

fDNS - Offline (1998 - 2010) - Free 3rd Level Domain Services

Page Load Speed

343 ms in total

First Response

25 ms

Resources Loaded

229 ms

Page Rendered

89 ms

fdns.net screenshot

About Website

Visit fdns.net now to see the best up-to-date FDNS content and also check out these interesting facts you probably never knew about fdns.net

Free 3rd Level Domain Services

Visit fdns.net

Key Findings

We analyzed Fdns.net page load time and found that the first response time was 25 ms and then it took 318 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

fdns.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.116

85/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

home

25 ms

core.js

4 ms

global.css

10 ms

jquery-1.8.2.min.js

10 ms

style.css

28 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 67% of them (6 requests) were addressed to the original Fdns.net, 22% (2 requests) were made to Pagead2.googlesyndication.com and 11% (1 request) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (36 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.6 kB (38%)

Content Size

92.0 kB

After Optimization

57.4 kB

In fact, the total size of Fdns.net main page is 92.0 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. Only 10% of websites need less resources to load. Images take 55.1 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.4 kB

  • Original 5.2 kB
  • After minification 5.0 kB
  • After compression 1.8 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 3.4 kB or 65% of the original size.

Image Optimization

-10%

Potential reduce by 5.3 kB

  • Original 55.1 kB
  • After minification 49.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. FDNS images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 41 B

  • Original 179 B
  • After minification 171 B
  • After compression 138 B

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 41 B or 23% of the original size.

CSS Optimization

-82%

Potential reduce by 25.9 kB

  • Original 31.5 kB
  • After minification 25.5 kB
  • After compression 5.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. Fdns.net needs all CSS files to be minified and compressed as it can save up to 25.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (43%)

Requests Now

7

After Optimization

4

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

Accessibility Review

fdns.net accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

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

fdns.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fdns.net SEO score

62

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fdns.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fdns.net 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

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