8 sec in total
943 ms
6.6 sec
467 ms
Click here to check amazing Shrine Kotolog content for Japan. Otherwise, check out these important facts you probably never knew about shrine.kotolog.jp
京都の人気神社の完全ガイド!縁結び・商売繁盛・合格祈願・安産祈願の神さま
Visit shrine.kotolog.jpWe analyzed Shrine.kotolog.jp page load time and found that the first response time was 943 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
shrine.kotolog.jp performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.5 s
1/100
25%
Value8.1 s
21/100
10%
Value130 ms
96/100
30%
Value0.168
71/100
15%
Value10.1 s
26/100
10%
943 ms
1226 ms
726 ms
724 ms
1482 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Shrine.kotolog.jp, 52% (46 requests) were made to Item.kotolog.jp and 7% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Item.kotolog.jp.
Page size can be reduced by 630.6 kB (24%)
2.6 MB
1.9 MB
In fact, the total size of Shrine.kotolog.jp main page is 2.6 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 38.4 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 38.4 kB or 78% of the original size.
Potential reduce by 16.3 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. Shrine Kotolog images are well optimized though.
Potential reduce by 515.6 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 515.6 kB or 71% of the original size.
Potential reduce by 60.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. Shrine.kotolog.jp needs all CSS files to be minified and compressed as it can save up to 60.3 kB or 85% of the original size.
Number of requests can be reduced by 37 (43%)
86
49
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shrine Kotolog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
shrine.kotolog.jp
943 ms
desktop.css
1226 ms
owl.carousel.css
726 ms
jquery.remodal.css
724 ms
jquery.min.js
1482 ms
owl.carousel.min.js
923 ms
jquery.leanModal.min.js
567 ms
adsbygoogle.js
7 ms
jquery-ui.js
2500 ms
jquery.cookie.js
739 ms
jquery.remodal.min.js
920 ms
social.js
921 ms
common.js
1129 ms
desktop.js
1103 ms
bgt
1278 ms
0.gif
934 ms
logo.png
206 ms
logo.png
205 ms
ico_search.png
206 ms
main01.png
1250 ms
main02.png
1111 ms
main03.png
1647 ms
654-1.jpg
584 ms
446-1.jpg
380 ms
8-1.jpg
579 ms
61-1.jpg
784 ms
486-1.jpg
1008 ms
227-1.jpg
973 ms
271-1.jpg
1236 ms
579-1.jpg
1417 ms
426-1.jpg
1306 ms
177-1.jpg
1360 ms
568-1.jpg
1359 ms
627-1.jpg
1750 ms
338-0.jpg
1851 ms
258-0.jpg
2782 ms
35-1.jpg
2061 ms
614-1.jpg
1858 ms
348-1.jpg
1810 ms
pagetop.png
1925 ms
doc1_off.png
1992 ms
doc2_off.png
2037 ms
doc3_off.png
2040 ms
doc4_off.png
2099 ms
ca-pub-6292020854220769.js
172 ms
zrt_lookup.html
164 ms
show_ads_impl.js
55 ms
p_ikitai.png
2133 ms
p_itta.png
2183 ms
ads
198 ms
osd.js
42 ms
ads
228 ms
arrow.png
2029 ms
ads
265 ms
ads
157 ms
abg.js
27 ms
2863936352242505869
63 ms
s
3 ms
m_js_controller.js
25 ms
x_button_blue2.png
58 ms
googlelogo_color_112x36dp.png
67 ms
7909082297893794676
42 ms
redir.html
90 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
8 ms
iframe.html
40 ms
sdk.js
171 ms
analytics.js
56 ms
button-only.gif
359 ms
bookmark_button.js
390 ms
widgets.js
41 ms
main01.png
2930 ms
main02.png
2083 ms
main03.png
3102 ms
collect
32 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
51 ms
collect
142 ms
like.php
208 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
34 ms
106 ms
ga-audiences
45 ms
xd_arbiter.php
172 ms
xd_arbiter.php
279 ms
qeKvIRsJabD.js
299 ms
LVx-xkvaJ0b.png
337 ms
jot
96 ms
562 ms
reset.css
10 ms
entry-button.css
11 ms
bbtn-l_v3.png
5 ms
shrine.kotolog.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-*] attributes do not match their roles
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
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
shrine.kotolog.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
shrine.kotolog.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
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 Shrine.kotolog.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 Shrine.kotolog.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.
shrine.kotolog.jp
Open Graph data is detected on the main page of Shrine Kotolog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: