6 sec in total
35 ms
5.3 sec
688 ms
Welcome to mystery.co.jp homepage info - get ready to check Mystery best content for Japan right away, or after learning these important things about mystery.co.jp
世界各国の上質なドラマをお届けする日本唯一のミステリードラマ専門チャンネル(旧AXNミステリー)。英国の本格ミステリーを中心に、ヨーロッパの話題作、人気小説が原作の日本のミステリーまで、選りすぐりのミステリードラマが集結!
Visit mystery.co.jpWe analyzed Mystery.co.jp page load time and found that the first response time was 35 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mystery.co.jp performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value32.2 s
0/100
25%
Value14.2 s
1/100
10%
Value2,460 ms
5/100
30%
Value0.926
3/100
15%
Value26.7 s
0/100
10%
35 ms
390 ms
77 ms
378 ms
390 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 64% of them (57 requests) were addressed to the original Mystery.co.jp, 9% (8 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Tr.line.me. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Mystery.co.jp.
Page size can be reduced by 804.2 kB (9%)
9.3 MB
8.5 MB
In fact, the total size of Mystery.co.jp main page is 9.3 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. 80% 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 9.0 MB which makes up the majority of the site volume.
Potential reduce by 49.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 6.9 kB, which is 11% 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 49.9 kB or 81% of the original size.
Potential reduce by 740.2 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. Mystery images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 12.6 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. Mystery.co.jp needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 75% of the original size.
Number of requests can be reduced by 30 (38%)
79
49
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mystery. 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 from 5 to 1 for CSS and as a result speed up the page load time.
mystery.co.jp
35 ms
www.mystery.co.jp
390 ms
gtm.js
77 ms
common.css
378 ms
top.css
390 ms
slick.css
392 ms
jquery-3.6.0.min.js
21 ms
slick.min.js
389 ms
common.js
385 ms
top.js
387 ms
js
47 ms
analytics.js
16 ms
collect
89 ms
collect
27 ms
css2
30 ms
css2
44 ms
l8w366oeb2wyg2g7g3jca1udvxg9gv.jpg
261 ms
g79hzj50s16jzeh0r423obqmyzubu0.jpg
436 ms
gzf7nvbjyz6jji0aw98qjo2zasv8vf.jpg
441 ms
s0egz13ww4bn9c74184sxmvcyt4gnm.jpg
435 ms
2y57gge0pmmoxo0xjxu8qb7m6p101b.jpg
440 ms
3m8mc0c4y96wvk0rxwiyp3goas93i4.jpg
439 ms
fgp40lv8gqzzxmnudi5fo9m3s4kzto.jpg
640 ms
n325qb0puq2jjlvaszu5u5hb6sgnxy.jpg
847 ms
v9wh6aaa97kjq9avx46v10h2rtpwnp.jpg
1548 ms
0r3hodrul8hjr6xp5c3w100gmdjs80.jpg
643 ms
rgs2p7u013g253ywrz0pnhoidy3y2r.jpg
847 ms
4r63wewtqnxm34j3vhrl5zgazvgy1h.jpg
1700 ms
xzqm9nzgepu8n0li9wtv79rrvjclr1.jpg
1013 ms
kb30z89f7sc2ujszb27dytsib4un7h.jpg
1014 ms
m7tlwrl9x8ms9j6k6abmbqfeg5ky5d.jpg
2079 ms
6oa72qesi0u5jzyq8yinsi2mibrh5j.jpg
1194 ms
program-schedule.json
1306 ms
top.json
1330 ms
pickup.json
1474 ms
column.json
1672 ms
information.json
1680 ms
keywords.json
1835 ms
logo_mystery_sp.svg
1858 ms
btn_howto_sp.svg
1970 ms
btn_menu.svg
2030 ms
btn_menu_close_blue.svg
2045 ms
mys_omikuji.png
2201 ms
icon_twitter_blue.svg
2229 ms
icon_facebook_blue.svg
2336 ms
logo_sky.svg
2355 ms
logo_jcom.svg
2402 ms
logo_hikaritv.svg
2419 ms
logo_auhikari.svg
2568 ms
logo_catv.svg
2595 ms
logo_mystery_footer.svg
2732 ms
icon_twitter.svg
2759 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75g.woff
335 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff
455 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff
542 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff
671 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff
538 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
454 ms
KFOlCnqEu92Fr1MmEU9vAA.woff
454 ms
KFOmCnqEu92Fr1Me5g.woff
495 ms
ytag.js
902 ms
conversion.js
137 ms
lt.js
302 ms
pb_conv2.js
42 ms
cmt.js
408 ms
cmt.js
739 ms
fbevents.js
133 ms
uwt.js
42 ms
pixel.js
54 ms
icon_facebook.svg
2612 ms
adsct
133 ms
adsct
244 ms
131 ms
bnr_axn.png
2448 ms
bnr_thecinema.png
2599 ms
icon_arrow.svg
2621 ms
icon_search.svg
2606 ms
icon_top_mv_arrow.svg
2679 ms
err.gif
732 ms
err.gif
737 ms
err.gif
759 ms
92 ms
3gwx8tcnhjm9qzit0cq9dm6tesae5k.jpg
1675 ms
1xza8cgudwzezm96lkvtvquv3sscrw.jpg
1672 ms
k9yb2m8hd3i7o8lcr6pkwnu2ia4k5k.png
1633 ms
m3zvk2ootzpl5oqzgaxc1zupjpn3jk.png
1831 ms
1owho6sf4rqwz46bceffte71p1wq6z.png
1830 ms
83jvek8lsylhrj3jmrz285dmetwx0p.jpg
1974 ms
icon_slide_arrow.svg
1991 ms
mystery.co.jp accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
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
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
mystery.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
mystery.co.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mystery.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 Mystery.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.
mystery.co.jp
Open Graph data is detected on the main page of Mystery. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: