Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

fuzzballs.co

Fuzzballs - Official Store

Page Load Speed

5.1 sec in total

First Response

445 ms

Resources Loaded

2.5 sec

Page Rendered

2.2 sec

fuzzballs.co screenshot

About Website

Click here to check amazing Fuzzballs content. Otherwise, check out these important facts you probably never knew about fuzzballs.co

Welcome to the Fuzzballs official store! Find authentic apparel, plush toys, stationery, homeware and accessories as well as the latest comics, wallpapers and more made for fans of Fuzzballs. Join the...

Visit fuzzballs.co

Key Findings

We analyzed Fuzzballs.co page load time and found that the first response time was 445 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

fuzzballs.co performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

en-us

445 ms

constants.js

41 ms

pubsub.js

139 ms

global.js

46 ms

preloads.js

51 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 88% of them (99 requests) were addressed to the original Fuzzballs.co, 9% (10 requests) were made to Cdn.shopify.com and 1% (1 request) were made to Polyfill.io. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fuzzballs.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.0 kB (7%)

Content Size

4.9 MB

After Optimization

4.5 MB

In fact, the total size of Fuzzballs.co main page is 4.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 327.5 kB

  • Original 384.5 kB
  • After minification 334.5 kB
  • After compression 57.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. This page needs HTML code to be minified as it can gain 50.0 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 327.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 15 B

  • Original 4.2 MB
  • After minification 4.2 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. Fuzzballs images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 673 B

  • Original 240.8 kB
  • After minification 240.8 kB
  • After compression 240.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 2.8 kB

  • Original 36.2 kB
  • After minification 36.2 kB
  • After compression 33.4 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. Fuzzballs.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (57%)

Requests Now

108

After Optimization

46

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

Accessibility Review

fuzzballs.co 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

[id] attributes on active, focusable elements are not unique

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 IDs are not unique

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

Best Practices

fuzzballs.co best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fuzzballs.co SEO score

84

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fuzzballs.co 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 Fuzzballs.co 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 data is detected on the main page of Fuzzballs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: