Tools & Wizards About Us
we-dok.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

we-dok.jp

ウィドック

Page Load Speed

1.7 sec in total

First Response

533 ms

Resources Loaded

806 ms

Page Rendered

363 ms

we-dok.jp screenshot

About Website

Welcome to we-dok.jp homepage info - get ready to check We Dok best content right away, or after learning these important things about we-dok.jp

Visit we-dok.jp

Key Findings

We analyzed We-dok.jp page load time and found that the first response time was 533 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

we-dok.jp performance score

0

Network Requests Diagram

we-dok.jp

533 ms

notosansjapanese.css

24 ms

NotoSansJP-Black.woff

83 ms

NotoSansJP-Bold.woff

194 ms

NotoSansJP-Medium.woff

210 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 11% of them (1 request) were addressed to the original We-dok.jp, 78% (7 requests) were made to Fonts.gstatic.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (533 ms) belongs to the original domain We-dok.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 413 B (34%)

Content Size

1.2 kB

After Optimization

819 B

  • HTML

In fact, the total size of We-dok.jp main page is 1.2 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. 70% of websites need less resources to load. HTML takes 1.2 kB which makes up the majority of the site volume.

HTML Optimization

-34%

Potential reduce by 413 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 819 B

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 413 B or 34% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • CSS

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Dok. According to our analytics all requests are already optimized.

Network Requests Diagram

we-dok.jp

we-dok.jp

533 ms

notosansjapanese.css

notosansjapanese.css

24 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

83 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

194 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

210 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

78 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

210 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

209 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

210 ms

SEO Factors

we-dok.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise We-dok.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 We-dok.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

we-dok.jp

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