Tools & Wizards About Us
w0w.co.jp screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

w0w.co.jp

Top | WOW

Page Load Speed

11.4 sec in total

First Response

529 ms

Resources Loaded

9.7 sec

Page Rendered

1.1 sec

w0w.co.jp screenshot

About Website

Click here to check amazing W 0 content for Japan. Otherwise, check out these important facts you probably never knew about w0w.co.jp

WOW is a visual design studio based in Tokyo, Sendai and London. We are involved in a wide field of design from advertising and commercial works to installation works for exhibition spaces, and also i...

Visit w0w.co.jp

Key Findings

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

Performance Metrics

w0w.co.jp performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

w0w.co.jp

529 ms

www.w0w.co.jp

523 ms

index.html

496 ms

jquery.min.js

10 ms

jquery-ui-1.9.2.custom.min.js

829 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 53% of them (38 requests) were addressed to the original W0w.co.jp, 42% (30 requests) were made to Material.cdnw0w.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.6 sec) relates to the external source Material.cdnw0w.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (11%)

Content Size

10.5 MB

After Optimization

9.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of W0w.co.jp main page is 10.5 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. 45% of websites need less resources to load. Images take 10.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 24.6 kB

  • Original 32.0 kB
  • After minification 31.9 kB
  • After compression 7.4 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 24.6 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 1.1 MB

  • Original 10.3 MB
  • After minification 9.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. W 0 images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 92.7 kB

  • Original 174.9 kB
  • After minification 151.9 kB
  • After compression 82.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 92.7 kB or 53% of the original size.

CSS Optimization

-83%

Potential reduce by 16.2 kB

  • Original 19.5 kB
  • After minification 13.8 kB
  • After compression 3.3 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. W0w.co.jp needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (22%)

Requests Now

65

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

w0w.co.jp

w0w.co.jp

529 ms

www.w0w.co.jp

www.w0w.co.jp

523 ms

index.html

index.html

496 ms

jquery.min.js

jquery.min.js

10 ms

jquery-ui-1.9.2.custom.min.js

jquery-ui-1.9.2.custom.min.js

829 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

511 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

348 ms

css3-mediaqueries.js

css3-mediaqueries.js

706 ms

commmon.js

commmon.js

554 ms

purl.js

purl.js

492 ms

works.js

works.js

866 ms

common.css

common.css

658 ms

main.css

main.css

852 ms

ga.js

ga.js

77 ms

filter

filter

171 ms

bg.gif

bg.gif

185 ms

wow_logo.gif

wow_logo.gif

182 ms

smp_menu.gif

smp_menu.gif

181 ms

smp_close.gif

smp_close.gif

183 ms

gotoTopBtn.gif

gotoTopBtn.gif

185 ms

filterClose.gif

filterClose.gif

328 ms

filter_activebg.gif

filter_activebg.gif

332 ms

googleMapIcon.gif

googleMapIcon.gif

343 ms

googleMapIcon_o.gif

googleMapIcon_o.gif

347 ms

footer_youtube.gif

footer_youtube.gif

353 ms

footer_youtube_o.gif

footer_youtube_o.gif

369 ms

footer_vimeo.gif

footer_vimeo.gif

492 ms

footer_vimeo_o.gif

footer_vimeo_o.gif

496 ms

footer_rss.gif

footer_rss.gif

511 ms

footer_rss_o.gif

footer_rss_o.gif

518 ms

footer_fb.gif

footer_fb.gif

529 ms

footer_fb_o.gif

footer_fb_o.gif

552 ms

footer_tw.gif

footer_tw.gif

656 ms

footer_tw_o.gif

footer_tw_o.gif

659 ms

logo_variation_8.gif

logo_variation_8.gif

681 ms

MetaWebPro-Normal.woff

MetaWebPro-Normal.woff

1029 ms

MetaSerifWebPro-LightItalic.woff

MetaSerifWebPro-LightItalic.woff

1052 ms

MetaWebPro-BookIta.woff

MetaWebPro-BookIta.woff

1099 ms

__utm.gif

__utm.gif

14 ms

collect

collect

59 ms

retrieve_en

retrieve_en

762 ms

3026.JPEG

3026.JPEG

1118 ms

3027.JPEG

3027.JPEG

939 ms

3037.JPEG

3037.JPEG

357 ms

3038.JPEG

3038.JPEG

925 ms

3015.JPEG

3015.JPEG

374 ms

3016.JPEG

3016.JPEG

882 ms

3008.JPEG

3008.JPEG

766 ms

3009.JPEG

3009.JPEG

778 ms

2978.JPEG

2978.JPEG

2469 ms

2979.JPEG

2979.JPEG

2274 ms

2969.JPEG

2969.JPEG

3119 ms

2970.JPEG

2970.JPEG

1783 ms

2956.JPEG

2956.JPEG

2675 ms

2957.JPEG

2957.JPEG

2500 ms

889.JPEG

889.JPEG

2910 ms

890.JPEG

890.JPEG

2465 ms

2932.JPEG

2932.JPEG

3761 ms

2933.JPEG

2933.JPEG

3556 ms

2919.JPEG

2919.JPEG

3806 ms

2920.JPEG

2920.JPEG

3751 ms

2908.JPEG

2908.JPEG

5654 ms

2909.JPEG

2909.JPEG

5669 ms

2885.JPEG

2885.JPEG

5181 ms

2886.JPEG

2886.JPEG

5509 ms

2902.JPEG

2902.JPEG

6550 ms

2903.JPEG

2903.JPEG

6471 ms

2799.JPEG

2799.JPEG

5546 ms

2800.JPEG

2800.JPEG

6263 ms

2869.JPEG

2869.JPEG

6469 ms

2870.JPEG

2870.JPEG

6576 ms

imgLoader.gif

imgLoader.gif

167 ms

Accessibility Review

w0w.co.jp accessibility score

73

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.

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

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

w0w.co.jp 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

SEO Factors

w0w.co.jp SEO score

92

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

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

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 W0w.co.jp 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 W0w.co.jp 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

w0w.co.jp

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