Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

2.8 sec in total

First Response

467 ms

Resources Loaded

2.1 sec

Page Rendered

226 ms

wafoos.com screenshot

About Website

Visit wafoos.com now to see the best up-to-date Wafoos content and also check out these interesting facts you probably never knew about wafoos.com

Wafoos - Japanese T-Shirts, apparel, bags, gifts and accessories featuring Kanji, Hiragana and Katakana Typography. Designs cover all aspects of Japanese culture from Anime to Zen. Create your own cus...

Visit wafoos.com

Key Findings

We analyzed Wafoos.com page load time and found that the first response time was 467 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wafoos.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value2.9 s

95/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

wafoos.com

467 ms

swfobject.js

216 ms

brains.css

202 ms

home.css

214 ms

addthis_widget.js

13 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 41% of them (20 requests) were addressed to the original Wafoos.com, 37% (18 requests) were made to Image.spreadshirtmedia.com and 4% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Image.spreadshirtmedia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 302.4 kB (36%)

Content Size

840.6 kB

After Optimization

538.2 kB

In fact, the total size of Wafoos.com main page is 840.6 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. 35% of websites need less resources to load. Javascripts take 393.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 45.2 kB

  • Original 62.8 kB
  • After minification 60.1 kB
  • After compression 17.6 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 45.2 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 6.3 kB

  • Original 374.0 kB
  • After minification 367.6 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. Wafoos images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 242.6 kB

  • Original 393.2 kB
  • After minification 392.9 kB
  • After compression 150.5 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 242.6 kB or 62% of the original size.

CSS Optimization

-77%

Potential reduce by 8.3 kB

  • Original 10.7 kB
  • After minification 8.7 kB
  • After compression 2.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. Wafoos.com needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (34%)

Requests Now

47

After Optimization

31

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

Accessibility Review

wafoos.com accessibility score

86

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

High

<frame> or <iframe> elements do not have a title

Best Practices

wafoos.com 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

wafoos.com SEO score

75

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

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wafoos.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wafoos.com 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 Wafoos. 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: