Tools & Wizards About Us
mostly.jp screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

mostly.jp

MOSTLY CLASSIC｜クラシック音楽を極めるための月刊情報誌 モーストリー・クラシック

Page Load Speed

4 sec in total

First Response

714 ms

Resources Loaded

3 sec

Page Rendered

303 ms

mostly.jp screenshot

About Website

Click here to check amazing MOSTLY content. Otherwise, check out these important facts you probably never knew about mostly.jp

クラシック音楽を極めるための月刊情報誌 モーストリー・クラシックの公式WEBサイトです。

Visit mostly.jp

Key Findings

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

Performance Metrics

mostly.jp performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

mostly.jp

714 ms

sankeidir.css

343 ms

import.css

348 ms

home.css

356 ms

ga.js

538 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 80% of them (40 requests) were addressed to the original Mostly.jp, 10% (5 requests) were made to Google.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Mostly.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.4 kB (24%)

Content Size

426.3 kB

After Optimization

325.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 14.0 kB

  • Original 20.2 kB
  • After minification 16.1 kB
  • After compression 6.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 4.1 kB, which is 20% 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 14.0 kB or 69% of the original size.

Image Optimization

-4%

Potential reduce by 12.8 kB

  • Original 300.1 kB
  • After minification 287.3 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. MOSTLY images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 48.4 kB

  • Original 74.9 kB
  • After minification 69.4 kB
  • After compression 26.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 48.4 kB or 65% of the original size.

CSS Optimization

-81%

Potential reduce by 25.2 kB

  • Original 31.0 kB
  • After minification 20.4 kB
  • After compression 5.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. Mostly.jp needs all CSS files to be minified and compressed as it can save up to 25.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (35%)

Requests Now

49

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mostly.jp

mostly.jp

714 ms

sankeidir.css

sankeidir.css

343 ms

import.css

import.css

348 ms

home.css

home.css

356 ms

ga.js

ga.js

538 ms

jsapi

jsapi

47 ms

jquery.min.js

jquery.min.js

23 ms

jquery-ui.min.js

jquery-ui.min.js

26 ms

jquery.belatedPNG.min.js

jquery.belatedPNG.min.js

361 ms

jquery.easing.compatibility.js

jquery.easing.compatibility.js

361 ms

yuga.js

yuga.js

372 ms

common.js

common.js

511 ms

reset.css

reset.css

175 ms

common.css

common.css

185 ms

menu.css

menu.css

201 ms

analytics.js

analytics.js

44 ms

17 ms

collect

collect

14 ms

default+en.css

default+en.css

3 ms

default+en.I.js

default+en.I.js

8 ms

bg_header.png

bg_header.png

348 ms

h1.png

h1.png

555 ms

globalnavi.png

globalnavi.png

730 ms

cover.jpg

cover.jpg

548 ms

specialfeature.png

specialfeature.png

174 ms

label_hatsubai.png

label_hatsubai.png

175 ms

label_teika.png

label_teika.png

344 ms

label_hyoushi.png

label_hyoushi.png

349 ms

btn_amazon.png

btn_amazon.png

515 ms

btn_fujisan.png

btn_fujisan.png

523 ms

bnr_bknum.png

bnr_bknum.png

642 ms

bnr_cddvd.png

bnr_cddvd.png

687 ms

bnr_nextnum.png

bnr_nextnum.png

695 ms

yokoku.jpg

yokoku.jpg

913 ms

bg_contentswrap.png

bg_contentswrap.png

736 ms

bg_contents.png

bg_contents.png

814 ms

rest.png

rest.png

857 ms

title_blog.png

title_blog.png

1041 ms

bg_footer.png

bg_footer.png

911 ms

pagetop_on.png

pagetop_on.png

918 ms

pagetop.png

pagetop.png

987 ms

btn_kokoku.png

btn_kokoku.png

1028 ms

btn_oshirase.png

btn_oshirase.png

1093 ms

copyright.png

copyright.png

1095 ms

btn_amazon_on.png

btn_amazon_on.png

1099 ms

btn_fujisan_on.png

btn_fujisan_on.png

1160 ms

bnr_bknum_on.png

bnr_bknum_on.png

1198 ms

bnr_cddvd_on.png

bnr_cddvd_on.png

1214 ms

bnr_nextnum_on.png

bnr_nextnum_on.png

1276 ms

Gfeeds

Gfeeds

464 ms

Accessibility Review

mostly.jp accessibility score

82

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

mostly.jp best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mostly.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 Mostly.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

mostly.jp

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