24.5 sec in total
525 ms
23.4 sec
623 ms
Click here to check amazing Dlove content for Japan. Otherwise, check out these important facts you probably never knew about dlove.jp
東京ディズニーランド・東京ディズニーシーのお土産・グッズ・キャラクターグリーティング・レストランやディズニーグッズ、イベントを紹介☆
Visit dlove.jpWe analyzed Dlove.jp page load time and found that the first response time was 525 ms and then it took 24 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
dlove.jp performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value3.7 s
58/100
25%
Value7.3 s
29/100
10%
Value220 ms
87/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
525 ms
1137 ms
17 ms
40 ms
29 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Dlove.jp, 96% (85 requests) were made to Mezzomiki.jp and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Mezzomiki.jp.
Page size can be reduced by 177.8 kB (19%)
946.6 kB
768.9 kB
In fact, the total size of Dlove.jp main page is 946.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. 50% of websites need less resources to load. Images take 651.6 kB which makes up the majority of the site volume.
Potential reduce by 159.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. 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 159.7 kB or 87% of the original size.
Potential reduce by 0 B
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. Dlove images are well optimized though.
Potential reduce by 206 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 17.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. Dlove.jp needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 24% of the original size.
Number of requests can be reduced by 18 (21%)
85
67
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dlove. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
dlove.jp
525 ms
mezzomiki.jp
1137 ms
wp-emoji-release.min.js
17 ms
style.min.css
40 ms
classic-themes.min.css
29 ms
wpp.css
77 ms
style.css
62 ms
normalize.css
28 ms
style.css
33 ms
style.css
44 ms
st-rankcss.php
370 ms
style.css
49 ms
st-themecss-loader.php
646 ms
wpp.min.js
791 ms
jquery.min.js
24 ms
bookmark_button.js
20 ms
base.js
70 ms
st-copy-text.js
73 ms
lazysizes.min.js
70 ms
ls.aspectratio.min.js
83 ms
gtm.js
188 ms
mezzomikilogo600.jpg
86 ms
st-themecss-loader.php
697 ms
IMG_5204-150x150.jpeg
84 ms
IMG_6979-150x150.jpeg
84 ms
IMG_1149-150x150.jpeg
84 ms
tokyo-disney-land-goods-600x300.jpg
1274 ms
tokyo-disney-sea-goods-2-600x300.jpg
1321 ms
IMG_9836-150x150.jpeg
132 ms
IMG_9830-150x150.jpeg
134 ms
IMG_9829-150x150.jpeg
133 ms
IMG_9819-150x150.jpeg
135 ms
IMG_9815-150x150.jpeg
845 ms
IMG_9807-150x150.jpeg
135 ms
IMG_9794-150x150.jpeg
136 ms
IMG_9788-150x150.jpeg
137 ms
IMG_9779-150x150.jpeg
862 ms
IMG_9773-150x150.jpeg
153 ms
IMG_9675-150x150.jpeg
153 ms
IMG_9676-150x150.jpeg
900 ms
IMG_9572-150x150.jpeg
1439 ms
IMG_9536-150x150.jpeg
857 ms
IMG_9510-150x150.jpeg
872 ms
IMG_2465-150x150.jpeg
1618 ms
IMG_8935-150x150.jpeg
895 ms
IMG_8796-150x150.jpeg
915 ms
IMG_8794-150x150.jpeg
911 ms
IMG_8790-150x150.jpeg
1670 ms
IMG_9183-150x150.jpeg
1666 ms
IMG_8771-150x150.jpeg
2243 ms
IMG_8766-150x150.jpeg
2297 ms
IMG_8758-150x150.jpeg
2433 ms
IMG_8754-150x150.jpeg
1632 ms
IMG_8752-150x150.jpeg
2388 ms
IMG_8741-150x150.jpeg
2426 ms
IMG_3034-150x150.jpeg
2405 ms
IMG_2700-3-150x150.jpg
2924 ms
stsvg.ttf
2230 ms
Z9H_5888-150x150.jpg
2984 ms
IMG_8364-150x150.jpeg
3059 ms
IMG_7203-150x150.jpeg
3296 ms
3
2655 ms
Z8H_2686-150x150.jpg
3040 ms
Z8H_2678-150x150.jpg
3636 ms
IMG_6735-150x150.jpeg
3114 ms
IMG_8009-150x150.jpeg
3665 ms
Z9Y_0339-150x150.jpeg
3766 ms
IMG_7314-150x150.jpeg
3779 ms
Z8H_2639-150x150.jpg
3856 ms
IMG_7221-150x150.jpeg
4196 ms
63BE5144-FE81-45DE-95E1-BACC920DC007-150x150.jpeg
3823 ms
IMG_7813-150x150.jpeg
3221 ms
85B6C1F8-0CEA-4733-A6C2-B293AE046E1A-150x150.jpeg
20011 ms
DSC_8869-150x150.jpg
3803 ms
DSC_5972-150x150.jpg
3397 ms
IMG_3013-150x150.jpeg
4164 ms
AC515BC6-7EBF-4A49-ADBB-C8EA40F07FE9-150x150.jpeg
4120 ms
DSC_5094-150x150.jpg
3448 ms
IMG_3227-150x150.jpeg
4441 ms
IMG_5470-100x100.jpeg
2484 ms
IMG_5204-100x100.jpeg
2622 ms
4809C57B-221E-4D05-9BE3-579203BE758D-100x100.jpeg
2249 ms
IMG_6979-100x100.jpeg
2263 ms
IMG_6314-100x100.jpeg
3022 ms
8932C7CF-FD9B-47F5-A719-C9014DC9FD3D-100x100.jpeg
2283 ms
IMG_5690-100x100.jpeg
2300 ms
IMG_4787-100x100.jpeg
2316 ms
IMG_5858-100x100.jpeg
2331 ms
IMG_3079-100x100.jpeg
3072 ms
dlove.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dlove.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dlove.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dlove.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 Dlove.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.
dlove.jp
Open Graph description is not detected on the main page of Dlove. 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: