4.8 sec in total
612 ms
3.5 sec
654 ms
Click here to check amazing Kukai content. Otherwise, check out these important facts you probably never knew about kukai.jpn.com
MINIBUTSUでは、京都の東寺、神護寺、醍醐寺、金剛峯寺の監修を受けた、確かな質のミニチュア仏像フィギュアを紹介・販売しています。
Visit kukai.jpn.comWe analyzed Kukai.jpn.com page load time and found that the first response time was 612 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
kukai.jpn.com performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value3.8 s
55/100
25%
Value3.0 s
94/100
10%
Value690 ms
43/100
30%
Value0.251
49/100
15%
Value4.9 s
77/100
10%
612 ms
1159 ms
304 ms
306 ms
309 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 69% of them (29 requests) were addressed to the original Kukai.jpn.com, 10% (4 requests) were made to Google-analytics.com and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Kukai.jpn.com.
Page size can be reduced by 167.4 kB (18%)
946.8 kB
779.3 kB
In fact, the total size of Kukai.jpn.com main page is 946.8 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. 35% of websites need less resources to load. Images take 806.0 kB which makes up the majority of the site volume.
Potential reduce by 17.3 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 17.3 kB or 71% of the original size.
Potential reduce by 82.6 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. Kukai images are well optimized though.
Potential reduce by 57.5 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 57.5 kB or 56% of the original size.
Potential reduce by 10.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. Kukai.jpn.com needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 75% of the original size.
Number of requests can be reduced by 18 (45%)
40
22
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kukai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
kukai.jpn.com
612 ms
www.kukai.jpn.com
1159 ms
common.css
304 ms
top.css
306 ms
common.css
309 ms
top.css
307 ms
css
100 ms
css
123 ms
jquery.min.js
123 ms
jquery.nivo.slider.pack.js
458 ms
nivo-slider.css
302 ms
ultracker.js
455 ms
logo2.png
231 ms
banner_top01.jpg
1014 ms
title_lineup.png
228 ms
17_thumb.jpg
345 ms
14_thumb.jpg
345 ms
18_thumb.jpg
473 ms
16_thumb.jpg
472 ms
15_thumb.jpg
481 ms
13_thumb.jpg
668 ms
12_thumb.jpg
681 ms
11_thumb.jpg
840 ms
10_thumb.jpg
840 ms
8_thumb.jpg
679 ms
7_thumb.jpg
845 ms
6_thumb.jpg
850 ms
5_thumb.jpg
1006 ms
logo_footer.gif
994 ms
all.js
158 ms
ga.js
147 ms
header_globalnavi.png
983 ms
bg-footer.jpg
986 ms
analytics.js
152 ms
225 ms
ga.utils.js
771 ms
collect
61 ms
xd_arbiter.php
82 ms
xd_arbiter.php
147 ms
beacon.gif
233 ms
__utm.gif
30 ms
276 ms
kukai.jpn.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
Form elements do not have associated labels
kukai.jpn.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
kukai.jpn.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kukai.jpn.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Kukai.jpn.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.
kukai.jpn.com
Open Graph description is not detected on the main page of Kukai. 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: