Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

joris.works

Joris Rigerl

Page Load Speed

3.2 sec in total

First Response

516 ms

Resources Loaded

2.6 sec

Page Rendered

92 ms

joris.works screenshot

About Website

Visit joris.works now to see the best up-to-date Joris content for United States and also check out these interesting facts you probably never knew about joris.works

Joris Rigerl is a digital designer based in Brooklyn, NY

Visit joris.works

Key Findings

We analyzed Joris.works page load time and found that the first response time was 516 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

joris.works performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.6 s

100/100

10%

Network Requests Diagram

joris.works

516 ms

jquery.min.js

30 ms

jquery-2.1.1.min.js

402 ms

jquery.smoothState.js

234 ms

imagesloaded.pkgd.min.js

233 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 58% of them (14 requests) were addressed to the original Joris.works, 17% (4 requests) were made to and 8% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Joris.works.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.1 kB (6%)

Content Size

2.2 MB

After Optimization

2.1 MB

In fact, the total size of Joris.works main page is 2.2 MB. 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 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 8.4 kB

  • Original 10.3 kB
  • After minification 9.5 kB
  • After compression 1.9 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 8.4 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.0 MB
  • After minification 2.0 MB

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. Joris images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 95.7 kB

  • Original 186.1 kB
  • After minification 186.1 kB
  • After compression 90.4 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 95.7 kB or 51% of the original size.

CSS Optimization

-85%

Potential reduce by 21.0 kB

  • Original 24.8 kB
  • After minification 24.5 kB
  • After compression 3.8 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. Joris.works needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (37%)

Requests Now

19

After Optimization

12

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

Accessibility Review

joris.works accessibility score

70

Accessibility Issues

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

joris.works 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

SEO Factors

joris.works 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 Joris.works 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 Joris.works 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 Joris. 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: