Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

mercstoria.happyelements.co.jp

メルクストーリア – 癒術士と鐘の音色 -(メルスト)公式サイト

Page Load Speed

3.5 sec in total

First Response

398 ms

Resources Loaded

2.4 sec

Page Rendered

728 ms

mercstoria.happyelements.co.jp screenshot

About Website

Click here to check amazing Mercstoria Happyelements content for Japan. Otherwise, check out these important facts you probably never knew about mercstoria.happyelements.co.jp

メルクストーリア(メルスト)の公式サイト。RPGの常識を突き破る!?ストーリー重視のコミカルファンタジー!! 超本格ライン型ストラテジーゲーム

Visit mercstoria.happyelements.co.jp

Key Findings

We analyzed Mercstoria.happyelements.co.jp page load time and found that the first response time was 398 ms and then it took 3.1 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

mercstoria.happyelements.co.jp performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.772

5/100

15%

TTI (Time to Interactive)

Value37.6 s

0/100

10%

Network Requests Diagram

mercstoria.happyelements.co.jp

398 ms

style.css

363 ms

venobox.css

362 ms

jquery-1.11.0.min.js

12 ms

respond.min.js

393 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 18% of them (16 requests) were addressed to the original Mercstoria.happyelements.co.jp, 28% (25 requests) were made to Dbcj6kgtik9tl.cloudfront.net and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mercstoria.happyelements.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Mercstoria.happyelements.co.jp main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.1 kB

  • Original 33.7 kB
  • After minification 29.8 kB
  • After compression 7.7 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.0 kB, which is 12% 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 26.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 1.8 kB

  • Original 1.0 MB
  • After minification 1.0 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. Mercstoria Happyelements images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 69.9 kB

  • Original 134.9 kB
  • After minification 119.1 kB
  • After compression 65.0 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 69.9 kB or 52% of the original size.

CSS Optimization

-90%

Potential reduce by 152.7 kB

  • Original 170.1 kB
  • After minification 121.9 kB
  • After compression 17.4 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. Mercstoria.happyelements.co.jp needs all CSS files to be minified and compressed as it can save up to 152.7 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (41%)

Requests Now

83

After Optimization

49

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

Accessibility Review

mercstoria.happyelements.co.jp accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

mercstoria.happyelements.co.jp best practices score

75

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

mercstoria.happyelements.co.jp SEO score

85

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

Links do not have descriptive text

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 Mercstoria.happyelements.co.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 Mercstoria.happyelements.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

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