7.1 sec in total
547 ms
5.8 sec
679 ms
Click here to check amazing Iseyama content for Japan. Otherwise, check out these important facts you probably never knew about iseyama.jp
伊勢山皇大神宮は、天照大御神を御祭神とし、「関東のお伊勢さま」と親しまれる、明治初年に国費を以て創建された神社であり、神奈川県の宗社、横浜の総鎮守です。
Visit iseyama.jpWe analyzed Iseyama.jp page load time and found that the first response time was 547 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
iseyama.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value9.3 s
1/100
25%
Value10.9 s
6/100
10%
Value470 ms
61/100
30%
Value0
100/100
15%
Value11.0 s
21/100
10%
547 ms
1661 ms
74 ms
50 ms
43 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 56% of them (34 requests) were addressed to the original Iseyama.jp, 23% (14 requests) were made to Static.xx.fbcdn.net and 7% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Iseyama.jp.
Page size can be reduced by 95.5 kB (3%)
3.3 MB
3.2 MB
In fact, the total size of Iseyama.jp main page is 3.3 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 15.1 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 3.2 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 15.1 kB or 74% of the original size.
Potential reduce by 78.1 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. Iseyama images are well optimized though.
Potential reduce by 1.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 939 B
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. Iseyama.jp needs all CSS files to be minified and compressed as it can save up to 939 B or 16% of the original size.
Number of requests can be reduced by 24 (43%)
56
32
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iseyama. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
iseyama.jp
547 ms
iseyama.jp
1661 ms
js
74 ms
css2
50 ms
font-awesome.min.css
43 ms
base_new.css
203 ms
style_new.css
399 ms
jquery-1.11.0.min.js
32 ms
slick.css
55 ms
slick-theme.min.css
68 ms
slick.min.js
84 ms
lib.js
773 ms
util.js
681 ms
init.js
698 ms
init.css
502 ms
20240615134923_p915-300x200.jpg
877 ms
yokohamajinnjameguri-300x200.jpg
895 ms
osirase-300x200.jpeg
897 ms
load_logo.svg
351 ms
logo.svg
367 ms
ig_logo_mono.png
211 ms
fb_logo_mono.png
342 ms
top_logo_wh.svg
265 ms
exhibition4.jpg
593 ms
exhibition4.jpg
459 ms
koshashin.jpg
689 ms
koshashin.jpg
701 ms
bn-wlp.jpg
898 ms
bn-wlp.jpg
653 ms
navi_about.jpg
1054 ms
navi_gokitou.jpg
951 ms
navi_wedding.jpg
1023 ms
navi_keidai.jpg
1038 ms
navi_omamori.jpg
1206 ms
navi_anniversary.jpg
1084 ms
map.png
1822 ms
page.php
103 ms
ajax-loader.gif
17 ms
uSNZLykqYPO.css
21 ms
DaPJf3IFK7Z.js
28 ms
o1ndYS2og_B.js
24 ms
8O2J-mJIMh1.js
25 ms
oOOj7ijtZAT.js
23 ms
RLVuU6AS6qq.js
24 ms
LHNn6iugDK2.js
26 ms
Pz75mA64-wJ.js
26 ms
T7FDTMzRV7g.js
57 ms
p55HfXW__mM.js
56 ms
25lpsvLC9vq.js
59 ms
0oAcl5WIW_m.js
58 ms
327337807_1367153937432140_3509147285351825121_n.jpg
62 ms
TnQZHpuibd7.js
10 ms
UXtr_j2Fwe-.png
8 ms
top1.jpg
899 ms
top2.jpg
680 ms
top3.jpg
701 ms
top4.jpg
1039 ms
banner_bg.jpg
678 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubA.ttf
85 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzWPebA.ttf
156 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2byYPebA.ttf
690 ms
iseyama.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
iseyama.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
iseyama.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 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 Iseyama.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 Iseyama.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.
iseyama.jp
Open Graph description is not detected on the main page of Iseyama. 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: