Tools & Wizards About Us
fjordaan.net screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fjordaan.net

Francois Jordaan - London, United Kingdom | about.me

Page Load Speed

1 sec in total

First Response

197 ms

Resources Loaded

649 ms

Page Rendered

173 ms

fjordaan.net screenshot

About Website

Click here to check amazing F Jordaan content. Otherwise, check out these important facts you probably never knew about fjordaan.net

I am a user experience designer in London, United Kingdom. Visit my company website.

Visit fjordaan.net

Key Findings

We analyzed Fjordaan.net page load time and found that the first response time was 197 ms and then it took 822 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

fjordaan.net performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

fjordaan.net

197 ms

francois.jordaan

64 ms

js

66 ms

geu7rrs.css

63 ms

2971b957.bundle.js

13 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Fjordaan.net, 58% (11 requests) were made to About.me and 21% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (310 ms) relates to the external source About.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.3 kB (31%)

Content Size

345.3 kB

After Optimization

240.0 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-77%

Potential reduce by 105.3 kB

  • Original 136.3 kB
  • After minification 136.2 kB
  • After compression 31.0 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 105.3 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 209.0 kB
  • After minification 209.0 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. F Jordaan images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

We found no issues to fix!

Requests Now

6

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F Jordaan. According to our analytics all requests are already optimized.

Network Requests Diagram

fjordaan.net

fjordaan.net

197 ms

francois.jordaan

francois.jordaan

64 ms

js

js

66 ms

geu7rrs.css

geu7rrs.css

63 ms

2971b957.bundle.js

2971b957.bundle.js

13 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

48 ms

p.css

p.css

22 ms

aboutme_fjordaan.net_1468356521_65.jpg

aboutme_fjordaan.net_1468356521_65.jpg

310 ms

proxima_nova_bold-punc.woff

proxima_nova_bold-punc.woff

20 ms

proxima_nova_bold-latin-a.woff

proxima_nova_bold-latin-a.woff

21 ms

proximanova-bold-webfont.woff

proximanova-bold-webfont.woff

29 ms

proxima_nova_reg-punc.woff

proxima_nova_reg-punc.woff

28 ms

proxima_nova_reg-latin-a.woff

proxima_nova_reg-latin-a.woff

28 ms

proximanova-regular-webfont.woff

proximanova-regular-webfont.woff

35 ms

proximanova-light-webfont.woff

proximanova-light-webfont.woff

34 ms

aboutme-glyphs.woff

aboutme-glyphs.woff

35 ms

d

d

4 ms

d

d

9 ms

d

d

14 ms

Accessibility Review

fjordaan.net accessibility score

80

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

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

fjordaan.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fjordaan.net SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

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 Fjordaan.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 Fjordaan.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

fjordaan.net

Open Graph data is detected on the main page of F Jordaan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: