5.6 sec in total
338 ms
5 sec
257 ms
Visit mapion.co.jp now to see the best up-to-date Mapion content for Japan and also check out these interesting facts you probably never knew about mapion.co.jp
日本の地図検索なら地図マピオン(Mapion)。地図は 住所 都道府県イラスト地図 地名 施設名 駅 路線 郵便番号から検索でき、目的地への乗換案内・ルート検索も簡単。便利なマップコード検索、標高(海抜)表示、キョリ測、天気予報も充実。
Visit mapion.co.jpWe analyzed Mapion.co.jp page load time and found that the first response time was 338 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mapion.co.jp performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value22.0 s
0/100
25%
Value13.0 s
2/100
10%
Value3,450 ms
2/100
30%
Value0.235
53/100
15%
Value24.6 s
0/100
10%
338 ms
220 ms
510 ms
181 ms
182 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 63% of them (64 requests) were addressed to the original Mapion.co.jp, 6% (6 requests) were made to Google-analytics.com and 5% (5 requests) were made to Cdn.ampproject.org. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Mapion.co.jp.
Page size can be reduced by 68.7 kB (4%)
1.8 MB
1.7 MB
In fact, the total size of Mapion.co.jp main page is 1.8 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. 75% 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 47.6 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 47.6 kB or 72% of the original size.
Potential reduce by 11.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. Mapion images are well optimized though.
Potential reduce by 8.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.3 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. Mapion.co.jp needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 18% of the original size.
Number of requests can be reduced by 42 (42%)
100
58
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mapion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
mapion.co.jp
338 ms
www.mapion.co.jp
220 ms
sidebar.css
510 ms
icon.css
181 ms
top.css
182 ms
flux_mapion_TM.min.js
50 ms
conversion.js
108 ms
publishertag.js
39 ms
jquery-1.11.1.min.js
198 ms
weatherNowTop.js
194 ms
top.js
195 ms
typeahead.bundle.min.js
735 ms
localsearchbox.js
734 ms
topics_top2014.js
736 ms
gpt.js
128 ms
apstag.js
126 ms
header_logo.png
34 ms
header_search_submit_off.gif
33 ms
map_read_img.png
34 ms
map_dummy.png
570 ms
map_btn01_off.png
570 ms
map_btn_hokkaido_tohoku_off.png
570 ms
map_btn_kanto_off.png
697 ms
map_btn_hokuriku_off.png
688 ms
map_btn_tokai_off.png
704 ms
map_btn_kansai_off.png
1088 ms
map_btn_chugoku_off.png
1080 ms
map_btn_shikoku_off.png
1079 ms
map_btn_kyusyu_off.png
1161 ms
pop_hokkaido_tohoku.png
1585 ms
pop_close.png
1395 ms
pop_kanto.png
1763 ms
pop_hokuriku.png
2095 ms
pop_toukai.png
2098 ms
pop_kansai.png
2156 ms
pop_chugoku.png
2231 ms
pop_shikoku.png
2419 ms
pop_kyusyu.png
2776 ms
gnav_sprite.png
2942 ms
bnr_recommend06.png
2606 ms
bnr_recommend02.png
2675 ms
bnr_recommend03.png
2738 ms
bnr_biz.jpg
3087 ms
bnr_ts.png
3114 ms
phonebook_logo.gif
2880 ms
qlife.gif
2917 ms
phonebook_banner_img.png
2998 ms
gtm.js
187 ms
head_top_bg.png
3420 ms
map_bg_main_illust.png
3687 ms
map_bg_main.png
3052 ms
icon_loupe.png
3134 ms
title_line01.png
3496 ms
pixel.gif
64 ms
pubads_impl.js
71 ms
pixel.gif
67 ms
icon_arrow02.gif
3436 ms
side_line.gif
2929 ms
bg_side_map_btn.png
2930 ms
js
147 ms
analytics.js
141 ms
weather.json
744 ms
weather.json
740 ms
syncframe
152 ms
21220494
188 ms
linkid.js
33 ms
login_user.html
2734 ms
CustomPageview.js
2857 ms
bg_primary_btn.png
2737 ms
collect
24 ms
collect
21 ms
collect
22 ms
collect
4 ms
collect
24 ms
collect
29 ms
collect
25 ms
ga-audiences
74 ms
ga-audiences
70 ms
ga-audiences
66 ms
icon_arrow_round.png
2618 ms
ob.js
24 ms
publishertag.ids.js
8 ms
side_ico.gif
2612 ms
phonebook_bg_02.png
2786 ms
phonebook_bg_01.png
2473 ms
phonebook_icon_sprite.gif
2491 ms
phonebook_bg_banner02.png
2584 ms
phonebook_bg_banner01.png
2574 ms
phonebook_bg_footer.png
2354 ms
phonebook_bg_footer_link.png
2199 ms
icon_pagetop.png
2050 ms
100.gif
1760 ms
ads
382 ms
container.html
24 ms
amp4ads-v0.js
50 ms
amp-ad-exit-0.1.js
76 ms
amp-analytics-0.1.js
81 ms
amp-fit-text-0.1.js
78 ms
amp-form-0.1.js
79 ms
12238987010552118110
134 ms
en.png
41 ms
icon.png
39 ms
mapion.co.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
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.
mapion.co.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mapion.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 Mapion.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 Mapion.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.
mapion.co.jp
Open Graph description is not detected on the main page of Mapion. 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: