8.3 sec in total
416 ms
7.2 sec
672 ms
Welcome to layton.jp homepage info - get ready to check Layton best content for Japan right away, or after learning these important things about layton.jp
レベルファイブが贈るナゾトキ・ファンタジーアドベンチャー「レイトン」シリーズ公式サイト
Visit layton.jpWe analyzed Layton.jp page load time and found that the first response time was 416 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
layton.jp performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value14.5 s
0/100
25%
Value16.6 s
0/100
10%
Value330 ms
76/100
30%
Value1.114
1/100
15%
Value18.7 s
3/100
10%
416 ms
700 ms
1191 ms
51 ms
36 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 92% of them (76 requests) were addressed to the original Layton.jp, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Layton.jp.
Page size can be reduced by 631.5 kB (9%)
6.7 MB
6.1 MB
In fact, the total size of Layton.jp main page is 6.7 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. 85% 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 6.4 MB which makes up the majority of the site volume.
Potential reduce by 44.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. 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 44.9 kB or 83% of the original size.
Potential reduce by 405.5 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. Layton images are well optimized though.
Potential reduce by 156.3 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 156.3 kB or 69% of the original size.
Potential reduce by 24.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. Layton.jp needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 84% of the original size.
Number of requests can be reduced by 12 (16%)
77
65
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Layton. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
layton.jp
416 ms
layton.jp
700 ms
www.layton.jp
1191 ms
gtm.js
51 ms
css2
36 ms
default.css
447 ms
shared.css
618 ms
top.css
529 ms
slick.css
591 ms
slick-theme.css
591 ms
img_logo_l5.svg
592 ms
flag_japan.png
685 ms
flag_english-us.png
876 ms
flag_english-uk.png
874 ms
flag_french.png
874 ms
flag_italian.png
875 ms
flag_german.png
875 ms
flag_spanish.png
876 ms
title.gif
1004 ms
title_read.png
1199 ms
news_title.gif
1078 ms
img_slide07_1129.png
1836 ms
img_slide06.png
1894 ms
img_slide05.png
1801 ms
img_slide01.png
2788 ms
img_slide03.png
3063 ms
img_slide04.png
3856 ms
img_slide_thumb07.png
1978 ms
img_slide_thumb06.png
2040 ms
img_slide_thumb05.png
2113 ms
img_slide_thumb01.png
2219 ms
img_slide_thumb03.png
2250 ms
img_slide_thumb04.png
2311 ms
js
90 ms
analytics.js
16 ms
collect
76 ms
jquery-3.6.0.min.js
2209 ms
picturefill.js
2274 ms
scrollTop.js
2371 ms
ticker.js
2391 ms
slick.min.js
2492 ms
h3_lmj.png
2646 ms
bnr_lmj_dx_plus.png
2639 ms
bnr_lmj.png
3272 ms
h3_layton.png
2565 ms
bnr_jouki_1129.png
2483 ms
bnr_jikan_app.png
2436 ms
bnr_akuma_app.png
2686 ms
bnr_fushigi_app.png
2662 ms
bnr_layton_fushigi.png
2589 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75g.woff
31 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75g.woff
122 ms
bnr_layton_akuma.png
2971 ms
bnr_layton_jikan.png
2559 ms
bnr_layton_majin.png
2614 ms
bnr_layton_kiseki.png
2618 ms
bnr_layton_tyou.png
2833 ms
bnr_laytonvs.png
2831 ms
bnr_laytonbros.png
2837 ms
bnr_contest_15th.png
3202 ms
bnr_wallpaper_15th.png
2821 ms
bnr_stamp_pc.png
2763 ms
bnr_anime_pc.png
2185 ms
banner_anime.png
2094 ms
banner_ad.gif
2181 ms
banner_gyakuten.gif
2100 ms
banner_fukuoka.gif
2109 ms
banner_london.gif
2065 ms
banner_kansyu.gif
2010 ms
banner_utahime.gif
2043 ms
title_bg.gif
2029 ms
bg_wood.gif
1963 ms
bg_woodh.gif
1954 ms
bg_slide.png
2506 ms
bg_content_t.gif
1825 ms
bg_content_b.gif
1827 ms
bg_content_loop.gif
1773 ms
bg_footer.gif
1759 ms
bg_footer_repeat.png
1812 ms
ajax-loader.gif
1647 ms
btn_slide_l.png
1719 ms
btn_slide_r.png
1720 ms
www.layton.jp
177 ms
layton.jp accessibility score
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
layton.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
layton.jp SEO score
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 Layton.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 Layton.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.
layton.jp
Open Graph description is not detected on the main page of Layton. 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: