5.3 sec in total
310 ms
4.5 sec
475 ms
Welcome to seichimap.jp homepage info - get ready to check Seichimap best content for Japan right away, or after learning these important things about seichimap.jp
全国3000箇所のアニメの聖地を網羅!全ての聖地を地図とストリービューで確認ができます。アニメの作品名、地名から全国の聖地を検索できます。聖地巡礼マップで気になる聖地を探しましょう。
Visit seichimap.jpWe analyzed Seichimap.jp page load time and found that the first response time was 310 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
seichimap.jp performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value6.3 s
10/100
25%
Value12.8 s
3/100
10%
Value510 ms
57/100
30%
Value0.009
100/100
15%
Value14.3 s
9/100
10%
310 ms
870 ms
297 ms
894 ms
75 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 46% of them (24 requests) were addressed to the original Seichimap.jp, 8% (4 requests) were made to Seichi-production.s3.amazonaws.com and 8% (4 requests) were made to B.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Seichimap.jp.
Page size can be reduced by 560.4 kB (27%)
2.1 MB
1.5 MB
In fact, the total size of Seichimap.jp main page is 2.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. 30% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 21.0 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 21.0 kB or 69% of the original size.
Potential reduce by 240.7 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. Obviously, Seichimap needs image optimization as it can save up to 240.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 236.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 236.9 kB or 65% of the original size.
Potential reduce by 61.7 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. Seichimap.jp needs all CSS files to be minified and compressed as it can save up to 61.7 kB or 79% of the original size.
Number of requests can be reduced by 19 (39%)
49
30
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seichimap. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
seichimap.jp
310 ms
seichimap.jp
870 ms
application-b8a984948a35dbb3895c663e91d2a19f.css
297 ms
application-db5c24a7ca5319e618ed625480975982.js
894 ms
js
75 ms
autocomplete.js
1358 ms
bookmark_button.js
537 ms
analytics.js
103 ms
two_column_image.jpeg
800 ms
button-only@2x.png
203 ms
two_column_image.png
1281 ms
two_column_image.jpeg
973 ms
two_column_P1040664.JPG
1191 ms
icn_spot_here_01-0f9a1b8253931a42f485c900c358ff0f.png
194 ms
bg_top_ttl-42c17952d68886383a74c8fbe2a024e2.png
468 ms
img_meguru_top-f720aadbe47bd7ea09621080a26dc5ff.png
192 ms
logo_top-99bc2239d4f71c6b2dfd256065d46ee5.png
477 ms
txt_spot_num_5-928340408fd4216b31e67a50cca6fd61.png
334 ms
txt_spot_num_0-05f19fd09e93e099add30e9be9ed40ff.png
481 ms
icn_wish_tab-40deb23d38c3a233e1e9d6dca06a5164.png
482 ms
icn_spot_tab-cebda1039df68773d5596da204729366.png
481 ms
icn_engine_01-4e48d0a1d394ca3ca81e262c913774f7.png
483 ms
icn_spot_ttl_02-5b2732b04a21c6a2b187c9c6640ca8f0.png
612 ms
icn_arrow_02-e93f0b95acc875b8d0f4c123b16cae7d.png
623 ms
icn_spot_02-56983e42567f6a116bda8a078c92298d.png
628 ms
%E5%9B%B35.png
1067 ms
%E3%82%B0%E3%83%AB%E3%83%A1%E3%83%A9%E3%83%B3%E3%82%AD%E3%83%B3%E3%82%B0.png
1800 ms
%E8%81%96%E5%9C%B0%E3%83%95%E3%82%A9%E3%83%AD%E3%83%BC%E3%83%9C%E3%82%BF%E3%83%B3.png
1364 ms
[LINE]%E8%81%96%E5%9C%B0%E5%B7%A1%E7%A4%BC%E3%83%9E%E3%83%83%E3%83%97.png
1198 ms
%E5%9B%B31%20(2).png
1353 ms
%E8%81%96%E5%9C%B01.png
924 ms
icn_seen_01-f797a495f33db6a0f8da7ed6bb75b0f4.png
1073 ms
all.js
133 ms
widgets.js
50 ms
888 ms
collect
55 ms
collect
81 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
41 ms
collect
118 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
28 ms
80 ms
xd_arbiter.php
86 ms
jot
88 ms
reset.css
170 ms
entry-button.css
336 ms
bbtn-l_v3.png
168 ms
nr-768.min.js
53 ms
ping
37 ms
like.php
79 ms
9f3ed8ee9f
116 ms
rU2ubZ6l1Q5.js
80 ms
LVx-xkvaJ0b.png
84 ms
seichimap.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
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.
seichimap.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
seichimap.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 doesn't use 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 Seichimap.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 Seichimap.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.
seichimap.jp
Open Graph description is not detected on the main page of Seichimap. 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: