Tools & Wizards About Us
whatsin.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 44

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

whatsin.jp

雑誌・ムック｜ワッツイン｜M-ON! BOOKS - エムオン・エンタテインメント

Page Load Speed

5.1 sec in total

First Response

478 ms

Resources Loaded

4.4 sec

Page Rendered

192 ms

whatsin.jp screenshot

About Website

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

M-ON! BOOKSの雑誌・ムック。ワッツイン。

Visit whatsin.jp

Key Findings

We analyzed Whatsin.jp page load time and found that the first response time was 478 ms and then it took 4.6 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

whatsin.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.188

65/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

whatsin.jp

478 ms

www.whatsin.jp

529 ms

css

32 ms

reset.css

317 ms

layout.css

306 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 76% of them (16 requests) were addressed to the original Whatsin.jp, 10% (2 requests) were made to Google-analytics.com and 10% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Whatsin.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.2 kB (19%)

Content Size

531.6 kB

After Optimization

432.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatsin.jp main page is 531.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. 20% of websites need less resources to load. Images take 400.2 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 3.8 kB

  • Original 6.0 kB
  • After minification 4.9 kB
  • After compression 2.2 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 1.0 kB, which is 17% 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 3.8 kB or 64% of the original size.

Image Optimization

-6%

Potential reduce by 23.7 kB

  • Original 400.2 kB
  • After minification 376.5 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. Whatsin images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 63.0 kB

  • Original 113.9 kB
  • After minification 113.6 kB
  • After compression 50.9 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 63.0 kB or 55% of the original size.

CSS Optimization

-75%

Potential reduce by 8.7 kB

  • Original 11.6 kB
  • After minification 9.1 kB
  • After compression 2.8 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. Whatsin.jp needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (18%)

Requests Now

17

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsin.jp

whatsin.jp

478 ms

www.whatsin.jp

www.whatsin.jp

529 ms

css

css

32 ms

reset.css

reset.css

317 ms

layout.css

layout.css

306 ms

style.css

style.css

322 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

1182 ms

common.js

common.js

350 ms

ga.js

ga.js

45 ms

logo.png

logo.png

325 ms

top_ban.jpg

top_ban.jpg

1198 ms

h1.jpg

h1.jpg

1211 ms

f.png

f.png

364 ms

mokuji-min.jpg

mokuji-min.jpg

728 ms

hodan.png

hodan.png

739 ms

music.png

music.png

693 ms

news.png

news.png

706 ms

matsunoma.png

matsunoma.png

2178 ms

haOjnueK8Or1ztuuRtr8dvesZW2xOQ-xsNqO47m55DA.woff

haOjnueK8Or1ztuuRtr8dvesZW2xOQ-xsNqO47m55DA.woff

18 ms

km2iCywk7CnC11BE8pBNVPesZW2xOQ-xsNqO47m55DA.woff

km2iCywk7CnC11BE8pBNVPesZW2xOQ-xsNqO47m55DA.woff

19 ms

__utm.gif

__utm.gif

16 ms

Accessibility Review

whatsin.jp accessibility score

44

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

whatsin.jp best practices score

42

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

whatsin.jp SEO score

84

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Whatsin.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 Whatsin.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

whatsin.jp

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