Tools & Wizards About Us
fatboy.at screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

fatboy.at

Iconic Bean Bag Chairs and Furniture | Quality, Sustainable Design – Fatboy

Page Load Speed

3 sec in total

First Response

180 ms

Resources Loaded

2.5 sec

Page Rendered

315 ms

fatboy.at screenshot

About Website

Visit fatboy.at now to see the best up-to-date Fatboy content and also check out these interesting facts you probably never knew about fatboy.at

Fatboy has been bringing innovative, iconic, and quality lifestyle products to fans all over the world since conception in 2002 when it set out to create the perfect lounge: The Original Bean Bag C...

Visit fatboy.at

Key Findings

We analyzed Fatboy.at page load time and found that the first response time was 180 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fatboy.at performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value6,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.933

3/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

fatboy.at

180 ms

www.fatboy.com

511 ms

modernizr-a0a1255aea153f9d728f2050e1881e93.js

62 ms

home-251da5817e362352c78654cdea474ee6.css

80 ms

application-8465ae7616fea8005a0ed009742931b7.js

119 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fatboy.at, 24% (8 requests) were made to Cdn0.fatboy.com and 21% (7 requests) were made to Cdn3.fatboy.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Cdn0.fatboy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 842.2 kB (42%)

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fatboy.at main page is 2.0 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. 40% of websites need less resources to load. Images take 885.3 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 25.0 kB

  • Original 36.2 kB
  • After minification 36.1 kB
  • After compression 11.3 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 25.0 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 375 B

  • Original 885.3 kB
  • After minification 884.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. Fatboy images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 424.8 kB

  • Original 617.8 kB
  • After minification 617.8 kB
  • After compression 192.9 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 424.8 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 392.1 kB

  • Original 457.2 kB
  • After minification 454.2 kB
  • After compression 65.1 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. Fatboy.at needs all CSS files to be minified and compressed as it can save up to 392.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (46%)

Requests Now

26

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fatboy. 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.

Network Requests Diagram

fatboy.at

fatboy.at

180 ms

www.fatboy.com

www.fatboy.com

511 ms

modernizr-a0a1255aea153f9d728f2050e1881e93.js

modernizr-a0a1255aea153f9d728f2050e1881e93.js

62 ms

home-251da5817e362352c78654cdea474ee6.css

home-251da5817e362352c78654cdea474ee6.css

80 ms

application-8465ae7616fea8005a0ed009742931b7.js

application-8465ae7616fea8005a0ed009742931b7.js

119 ms

home-334029a908e2195ee2d57384da161023.js

home-334029a908e2195ee2d57384da161023.js

292 ms

application-8278ebfee72bc4720e7ef3422f9d82cd.css

application-8278ebfee72bc4720e7ef3422f9d82cd.css

363 ms

fbevents.js

fbevents.js

348 ms

gtm.js

gtm.js

387 ms

fatboy-edison-the-petit-v4.jpg

fatboy-edison-the-petit-v4.jpg

1554 ms

fatboy-pffh-v2.jpg

fatboy-pffh-v2.jpg

938 ms

fatboy-pablolucker_2.jpg

fatboy-pablolucker_2.jpg

1088 ms

twitter-92053d085e9c8c7d4600c0a03ecacdc2.svg

twitter-92053d085e9c8c7d4600c0a03ecacdc2.svg

321 ms

logo-33ba85edf64295b3a76bb997143393b7.svg

logo-33ba85edf64295b3a76bb997143393b7.svg

320 ms

instagram-0ee9ceb53de0377215d8ab1f06f2b9ad.svg

instagram-0ee9ceb53de0377215d8ab1f06f2b9ad.svg

356 ms

pinterest-1ebc47bfa1419063c92e55db15e7cc0c.svg

pinterest-1ebc47bfa1419063c92e55db15e7cc0c.svg

355 ms

fatboy-original-red-v2.jpg

fatboy-original-red-v2.jpg

353 ms

youtube-a0ab9c16445ff6651057662c34656994.svg

youtube-a0ab9c16445ff6651057662c34656994.svg

317 ms

top_link-106cf3e6b9e5d5d59f51c8668ca65b54.png

top_link-106cf3e6b9e5d5d59f51c8668ca65b54.png

298 ms

facebook-00f882379214a369e0a5430630d9fc05.svg

facebook-00f882379214a369e0a5430630d9fc05.svg

321 ms

themix-5-regular-webfont.woff

themix-5-regular-webfont.woff

248 ms

themix-9-black-webfont.woff

themix-9-black-webfont.woff

183 ms

themix-9-blackcaps-webfont.woff

themix-9-blackcaps-webfont.woff

209 ms

fontawesome-webfont-91038c690f1d853da04628fd4e00feea.woff

fontawesome-webfont-91038c690f1d853da04628fd4e00feea.woff

242 ms

themix-7-boldcaps-webfont.woff

themix-7-boldcaps-webfont.woff

246 ms

ajax-loader-89b7afef6afed1756b46d7a8b5dc629d.gif

ajax-loader-89b7afef6afed1756b46d7a8b5dc629d.gif

91 ms

111 ms

analytics.js

analytics.js

24 ms

ec.js

ec.js

32 ms

collect

collect

23 ms

collect

collect

25 ms

collect

collect

49 ms

nr-885.min.js

nr-885.min.js

103 ms

Accessibility Review

fatboy.at accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

fatboy.at 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

fatboy.at SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

fatboy.at

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