Access dqmp.jp. 冒険の記録 | ドラクエ・パラダイス(ドラパラ)ドラゴンクエスト公式サイト

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.498

16/100

15%

TTI (Time to Interactive)

Value13.3 s

11/100

10%

www.dragonquest.jp

1081 ms

template_rsp3.css

140 ms

common2.css

96 ms

index2.css

121 ms

global-https.js

123 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dqmp.jp, 7% (7 requests) were made to Jp.square-enix.com and 6% (6 requests) were made to I.ytimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Dragonquest.jp.

Content Size

12.1 MB

After Optimization

11.1 MB

In fact, the total size of Dqmp.jp main page is 12.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. Only a small number of websites need less resources to load. Images take 11.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 57.4 kB

Original 67.3 kB
After minification 58.5 kB
After compression 9.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. This page needs HTML code to be minified as it can gain 8.8 kB, which is 13% 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 57.4 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 846.1 kB

Original 11.8 MB
After minification 10.9 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. Dqmp images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 123.7 kB

Original 227.6 kB
After minification 226.5 kB
After compression 103.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 123.7 kB or 54% of the original size.

CSS Optimization

-2%

Potential reduce by 689 B

Original 28.9 kB
After minification 28.9 kB
After compression 28.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. Dqmp.jp has all CSS files already compressed.

Requests Now

101

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Document uses 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 Dqmp.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 Dqmp.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

dqmp.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

冒険の記録 | ドラクエ・パラダイス(ドラパラ)ドラゴンクエスト公式サイト | SQUARE ENIX

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)