13.2 sec in total
3.3 sec
9.4 sec
518 ms
Visit kimobile.com now to see the best up-to-date K I MOBILE content for Japan and also check out these interesting facts you probably never knew about kimobile.com
北海道札幌市にあるイタリア・フランス車をメインとしたレストアや販売を手がけるクラシックカーショップです。
Visit kimobile.comWe analyzed Kimobile.com page load time and found that the first response time was 3.3 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
kimobile.com performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value18.7 s
0/100
25%
Value21.3 s
0/100
10%
Value130 ms
96/100
30%
Value0.167
71/100
15%
Value14.1 s
10/100
10%
3304 ms
640 ms
1007 ms
1035 ms
524 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 86% of them (99 requests) were addressed to the original Kimobile.com, 10% (11 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Kimobile.com.
Page size can be reduced by 593.1 kB (16%)
3.7 MB
3.1 MB
In fact, the total size of Kimobile.com main page is 3.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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 73.8 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 13.8 kB, which is 16% 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 73.8 kB or 87% of the original size.
Potential reduce by 37.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. K I MOBILE images are well optimized though.
Potential reduce by 312.4 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 312.4 kB or 68% of the original size.
Potential reduce by 169.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. Kimobile.com needs all CSS files to be minified and compressed as it can save up to 169.3 kB or 87% of the original size.
Number of requests can be reduced by 47 (46%)
103
56
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of K I MOBILE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.kimobile.com
3304 ms
base.css
640 ms
animate.css
1007 ms
jquery-1.12.1.min.js
1035 ms
jquery.collapser.min.js
524 ms
slider-pro.min.css
702 ms
jquery.sliderPro.min.js
1226 ms
owl.carousel.css
798 ms
owl.theme2.css
872 ms
owl.carousel.min.js
1055 ms
elements.css
958 ms
jquery.mmenu.all.css
1053 ms
jquery.mmenu.all.min.js
1276 ms
fancybox.css
1005 ms
jquery.js
1382 ms
jquery-migrate.min.js
1073 ms
jquery.fancybox.js
1074 ms
css
26 ms
css
38 ms
notosansjapanese.css
46 ms
wp-embed.min.js
647 ms
vehicle.css
179 ms
archive.css
178 ms
single.css
180 ms
parts.css
202 ms
ga.js
15 ms
wp-emoji-release.min.js
177 ms
__utm.gif
13 ms
site_pc.css
177 ms
site_pc_top.js
161 ms
logo.png
243 ms
logo_sp.png
241 ms
icon_inquiry.gif
243 ms
mainvisual_logo.png
243 ms
mainvisual01.jpg
670 ms
mainvisual02.jpg
671 ms
mainvisual03.jpg
864 ms
mainvisual04.jpg
865 ms
mainvisual05.jpg
1263 ms
mainvisual06.jpg
667 ms
mainvisual07.jpg
864 ms
mainvisual08.jpg
672 ms
mainvisual09.jpg
862 ms
mainvisual10.jpg
954 ms
mainvisual11.jpg
1005 ms
dayx.cgi
1103 ms
dayx.cgi
1600 ms
dayx.cgi
1692 ms
about-ki_heading.png
1112 ms
IMG_4872-250x250.jpg
1177 ms
IMG_4852-250x250.jpg
1277 ms
IMG_0338-250x250.jpg
1272 ms
IMG_4769-250x250.jpg
1341 ms
%EF%BD%89%EF%BD%90%EF%BD%88%EF%BD%8F%EF%BD%8E%EF%BD%85%E7%94%BB%E5%83%8F-005-1-250x250.jpg
1614 ms
%EF%BD%89%EF%BD%90%EF%BD%88%EF%BD%8F%EF%BD%8E%EF%BD%85%E7%94%BB%E5%83%8F-010-250x250.jpg
1438 ms
IMG_4737-250x250.jpg
1452 ms
IMG_4716-250x250.jpg
1516 ms
IMG_4519_R-250x250.jpg
1598 ms
IMG_4439-250x250.jpg
1628 ms
IMG_4366-250x250.jpg
1684 ms
1450233917_elements010-250x250.jpg
2123 ms
1447924069_elements010-250x250.jpg
1756 ms
1416646897_elements010-250x250.jpg
1773 ms
1454986395_elements0100-250x250.jpg
1754 ms
1432701162_elements010-250x250.jpg
1703 ms
IMG_4655-250x250.jpg
2156 ms
IMG_4411-250x250.jpg
1690 ms
002-250x250.jpg
1710 ms
001-250x250.jpg
1744 ms
sKd0EMYPAh5PYCRKSryvW6CWcynf_cDxXwCLxiixG1c.ttf
410 ms
32nyIRHyCu6iqEka_hbKsonF5uFdDttMLvmWuJdhhgs.ttf
410 ms
NotoSansJP-Regular.woff
422 ms
NotoSansJP-Medium.woff
413 ms
NotoSansJP-DemiLight.woff
419 ms
NotoSansJP-Light.woff
415 ms
NotoSansJP-Thin.woff
415 ms
NotoSansJP-Bold.woff
417 ms
NotoSansJP-Black.woff
423 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
421 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
421 ms
%EF%BD%89%EF%BD%90%EF%BD%88%EF%BD%8F%EF%BD%8E%EF%BD%85%E7%94%BB%E5%83%8F-002-250x250.jpg
1782 ms
bnr_side_a8.png
1413 ms
bnr_side_tsubushibu.png
1454 ms
bnr_side_autoparts.png
1489 ms
bnr_side_event_numazu.png
1511 ms
bnr_side_goods.png
1378 ms
bnr_side_recruit.png
1604 ms
collapse.gif
1441 ms
expand.gif
1454 ms
sp-buttons_bg.jpg
1403 ms
icon_gm01.png
1396 ms
icon_gm02.png
1374 ms
icon_gm03.png
1398 ms
icon_gm04.png
1347 ms
icon_phone.png
1310 ms
about-ki_bg.png
1925 ms
about-ki_more.png
1362 ms
icon_gorudini.png
1311 ms
heading_h3_after.gif
1249 ms
more_before.png
1241 ms
icon_a110.png
1228 ms
icon_alfa.png
1212 ms
icon_fiat500.png
1220 ms
caption_bg.png
1249 ms
post_h4_before.gif
1233 ms
icon_category-list.png
1232 ms
arrow_title.png
1292 ms
icon_pagetop.png
1245 ms
logo_footer.png
1249 ms
icon_footer-list.png
1220 ms
icon_gmaps.png
1246 ms
footer_gordini.png
1396 ms
openhand.cur
1232 ms
prev.gif
1214 ms
next.gif
1189 ms
kimobile.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
kimobile.com 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
kimobile.com 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kimobile.com 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 Kimobile.com 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.
kimobile.com
Open Graph description is not detected on the main page of K I MOBILE. 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: