9.9 sec in total
604 ms
8.5 sec
784 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 604 ms and then it took 9.3 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
Value5.6 s
5/100
10%
Value20.7 s
0/100
25%
Value13.9 s
1/100
10%
Value610 ms
49/100
30%
Value0.588
11/100
15%
Value18.7 s
3/100
10%
604 ms
847 ms
408 ms
643 ms
553 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 94% of them (31 requests) were addressed to the original Layton.jp, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Layton.jp.
Page size can be reduced by 26.6 kB (4%)
718.9 kB
692.3 kB
In fact, the total size of Layton.jp main page is 718.9 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. 30% of websites need less resources to load. Images take 682.5 kB which makes up the majority of the site volume.
Potential reduce by 8.2 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 8.2 kB or 69% of the original size.
Potential reduce by 12.4 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 34 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 6.0 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 6.0 kB or 82% of the original size.
We found no issues to fix!
31
31
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Layton. According to our analytics all requests are already optimized.
layton.jp
604 ms
www.layton.jp
847 ms
style.css
408 ms
btn_layton_vs.jpg
643 ms
btn_mystery.jpg
553 ms
book_banner.jpg
552 ms
bnTaiken02.gif
374 ms
bnTaiken.gif
593 ms
bnTago.gif
743 ms
ad_banner.jpg
804 ms
gyakuten_banner.jpg
846 ms
bn_navi.jpg
755 ms
london_life.gif
946 ms
bn_movie.jpg
986 ms
ds.gif
1107 ms
coro.gif
1129 ms
ga.js
84 ms
ttl.jpg
916 ms
bg_container.jpg
791 ms
ttl_hit.jpg
902 ms
layton01.jpg
936 ms
layton02.jpg
1172 ms
layton03.jpg
1192 ms
syukka.jpg
1146 ms
layton04.jpg
1711 ms
layton05.jpg
1257 ms
layton06.jpg
1288 ms
ttl_new02_150407.jpg
1437 ms
layton7_1508.jpg
1651 ms
bg.gif
1559 ms
footer_top.jpg
1655 ms
footer_logo.jpg
6622 ms
__utm.gif
12 ms
layton.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
SHIFT_JIS
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Layton.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
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: