Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

decker.design

Thomas Decker // UX/UI Design Portfolio

Page Load Speed

1 sec in total

First Response

181 ms

Resources Loaded

724 ms

Page Rendered

109 ms

About Website

Click here to check amazing Decker content. Otherwise, check out these important facts you probably never knew about decker.design

Bring your business into the modern age with a custom web design solution that engages users, drives sales & helps your business achieve its goals.

Visit decker.design

Key Findings

We analyzed Decker.design page load time and found that the first response time was 181 ms and then it took 833 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

decker.design performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

decker.design

181 ms

decker.design

255 ms

suspendedpage.cgi

209 ms

suspended.css

40 ms

css2

31 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 38% of them (3 requests) were addressed to the original Decker.design, 25% (2 requests) were made to Bluehost-cdn.com and 25% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (255 ms) belongs to the original domain Decker.design.

Page Optimization Overview & Recommendations

Page size can be reduced by 394 B (1%)

Content Size

39.2 kB

After Optimization

38.8 kB

In fact, the total size of Decker.design main page is 39.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 38.0 kB which makes up the majority of the site volume.

HTML Optimization

-43%

Potential reduce by 349 B

  • Original 819 B
  • After minification 817 B
  • After compression 470 B

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

Image Optimization

-0%

Potential reduce by 0 B

  • Original 38.0 kB
  • After minification 38.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. Decker images are well optimized though.

CSS Optimization

-12%

Potential reduce by 45 B

  • Original 372 B
  • After minification 372 B
  • After compression 327 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. Decker.design needs all CSS files to be minified and compressed as it can save up to 45 B or 12% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

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

Accessibility Review

decker.design accessibility score

93

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

Document doesn't have a <title> element

Best Practices

decker.design best practices score

83

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

Displays images with incorrect aspect ratio

SEO Factors

decker.design SEO score

77

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Decker.design can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Decker.design 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 Decker. 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: