Tools & Wizards About Us
wemake.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

wemake.jp

Wemake(ウィーメイク)

Page Load Speed

8.3 sec in total

First Response

1.6 sec

Resources Loaded

5.3 sec

Page Rendered

1.4 sec

wemake.jp screenshot

About Website

Click here to check amazing Wemake content for Japan. Otherwise, check out these important facts you probably never knew about wemake.jp

Wemakeは企画を求める企業と、素晴らしいスキルを持つ個人をつなぎ、これまでにない新商品や新規事業を生み出すプラットフォームです。

Visit wemake.jp

Key Findings

We analyzed Wemake.jp page load time and found that the first response time was 1.6 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

wemake.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,310 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

www.wemake.jp

1607 ms

all.css

54 ms

application-a5003d00b3cd84e99786a58bf88c49d8ffc229a939ab81e73f15b5204a613534.css

144 ms

main-b3df707bd5141ab38bf3.css

723 ms

application-8b77f14bffe8b3bce4a5b3e2774c5975e6f43e9952b02032de47c8b95e50308c.js

997 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 12% of them (9 requests) were addressed to the original Wemake.jp, 54% (40 requests) were made to S3.ap-northeast-1.amazonaws.com and 7% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source S3.ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 712.4 kB (18%)

Content Size

4.1 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 90.8 kB

  • Original 117.8 kB
  • After minification 110.4 kB
  • After compression 26.9 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 90.8 kB or 77% of the original size.

Image Optimization

-10%

Potential reduce by 279.9 kB

  • Original 2.8 MB
  • After minification 2.6 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. Wemake images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 332.9 kB

  • Original 892.7 kB
  • After minification 892.7 kB
  • After compression 559.7 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 332.9 kB or 37% of the original size.

CSS Optimization

-4%

Potential reduce by 8.8 kB

  • Original 201.0 kB
  • After minification 199.0 kB
  • After compression 192.2 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. Wemake.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

67

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.wemake.jp

www.wemake.jp

1607 ms

all.css

all.css

54 ms

application-a5003d00b3cd84e99786a58bf88c49d8ffc229a939ab81e73f15b5204a613534.css

application-a5003d00b3cd84e99786a58bf88c49d8ffc229a939ab81e73f15b5204a613534.css

144 ms

main-b3df707bd5141ab38bf3.css

main-b3df707bd5141ab38bf3.css

723 ms

application-8b77f14bffe8b3bce4a5b3e2774c5975e6f43e9952b02032de47c8b95e50308c.js

application-8b77f14bffe8b3bce4a5b3e2774c5975e6f43e9952b02032de47c8b95e50308c.js

997 ms

api.js

api.js

34 ms

main-b3797a246b34fd472525.js

main-b3797a246b34fd472525.js

861 ms

css2

css2

94 ms

css2

css2

111 ms

css

css

116 ms

gtm.js

gtm.js

302 ms

sdk.js

sdk.js

288 ms

original.png

original.png

1428 ms

wemake-mv_pc.png

wemake-mv_pc.png

345 ms

wemake_logo-bee5afb4b4e1f3bf7e92.png

wemake_logo-bee5afb4b4e1f3bf7e92.png

343 ms

icon-login-5d39ba77dd153b2486b9.svg

icon-login-5d39ba77dd153b2486b9.svg

343 ms

original.png

original.png

1174 ms

original.png

original.png

1193 ms

original.png

original.png

1175 ms

original.jpeg

original.jpeg

1318 ms

original.png

original.png

1171 ms

original.jpg

original.jpg

1338 ms

original.png

original.png

1480 ms

original.png

original.png

1639 ms

original.png

original.png

1499 ms

original.jpg

original.jpg

1481 ms

original.png

original.png

1504 ms

original.png

original.png

1586 ms

original.png

original.png

1642 ms

original.png

original.png

1640 ms

original.png

original.png

1659 ms

original.png

original.png

1667 ms

original.png

original.png

1746 ms

original.jpg

original.jpg

1803 ms

original.png

original.png

1802 ms

original.png

original.png

1809 ms

original.png

original.png

1820 ms

original.png

original.png

1828 ms

original.png

original.png

1906 ms

original.png

original.png

2003 ms

original.jpg

original.jpg

1976 ms

original.jpg

original.jpg

1981 ms

original.png

original.png

1979 ms

original.jpg

original.jpg

2439 ms

original.png

original.png

2066 ms

original.png

original.png

2139 ms

original.png

original.png

2141 ms

original.png

original.png

2143 ms

original.png

original.png

2178 ms

original.png

original.png

2230 ms

original.jpeg

original.jpeg

2303 ms

original.png

original.png

291 ms

original.png

original.png

236 ms

original.jpg

original.jpg

236 ms

start_header_bg-93413a82efb41f650cae.jpg

start_header_bg-93413a82efb41f650cae.jpg

505 ms

fa-regular-400.woff

fa-regular-400.woff

155 ms

fa-light-300.woff

fa-light-300.woff

233 ms

fa-solid-900.woff

fa-solid-900.woff

233 ms

recaptcha__en.js

recaptcha__en.js

233 ms

sdk.js

sdk.js

34 ms

anchor

anchor

36 ms

styles__ltr.css

styles__ltr.css

5 ms

recaptcha__en.js

recaptcha__en.js

12 ms

HLDS0lGvjhaHZ-h3T_KWQdivWM70PjtZZZPniKjPEwQ.js

HLDS0lGvjhaHZ-h3T_KWQdivWM70PjtZZZPniKjPEwQ.js

85 ms

webworker.js

webworker.js

77 ms

logo_48.png

logo_48.png

65 ms

recaptcha__en.js

recaptcha__en.js

224 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

24 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

27 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

30 ms

original.png

original.png

1288 ms

original.jpg

original.jpg

1299 ms

original.png

original.png

1177 ms

original.png

original.png

1358 ms

Accessibility Review

wemake.jp accessibility score

61

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

wemake.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

wemake.jp SEO score

85

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

wemake.jp

Open Graph data is detected on the main page of Wemake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: