10.6 sec in total
1.8 sec
8.3 sec
501 ms
Visit ee-tera.com now to see the best up-to-date Ee Tera content and also check out these interesting facts you probably never knew about ee-tera.com
現代に生きるみなさんとお寺をつなぐお寺検索サイトです。おすすめの寺院や季節のイベントなど、各種情報を掲載しています。
Visit ee-tera.comWe analyzed Ee-tera.com page load time and found that the first response time was 1.8 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ee-tera.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value4.4 s
39/100
25%
Value7.2 s
30/100
10%
Value0 ms
100/100
30%
Value0.004
100/100
15%
Value3.8 s
89/100
10%
1782 ms
186 ms
587 ms
1102 ms
2105 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 96% of them (47 requests) were addressed to the original Ee-tera.com, 4% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Ee-tera.com.
Page size can be reduced by 248.4 kB (19%)
1.3 MB
1.1 MB
In fact, the total size of Ee-tera.com main page is 1.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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 8.9 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 8.9 kB or 69% of the original size.
Potential reduce by 150.2 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. Obviously, Ee Tera needs image optimization as it can save up to 150.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 71.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 71.3 kB or 60% of the original size.
Potential reduce by 18.1 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. Ee-tera.com needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 78% of the original size.
Number of requests can be reduced by 13 (28%)
47
34
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ee Tera. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
ee-tera.com
1782 ms
index.css
186 ms
jquery-1.3.2.min.js
587 ms
jquery.pngFix.js
1102 ms
resizeFont.js
2105 ms
jquery.flash.js
355 ms
jquery.curvycorners.min.js
2325 ms
externallink.js
3126 ms
swfobject.js
526 ms
local.css
514 ms
global.css
172 ms
dc.js
40 ms
news.php
185 ms
logo.png
148 ms
fontsize.jpg
204 ms
fontsize_s.gif
191 ms
fontsize_m.gif
187 ms
fontsize_l.gif
155 ms
global_nav_bg.jpg
439 ms
global-nav.png
308 ms
global-nav05.png
355 ms
main_bg.jpg
545 ms
contents_header_bg.jpg
564 ms
contents_header_main_bg.jpg
595 ms
contents_header_flash.jpg
1231 ms
label01_2.jpg
526 ms
greeting_bg.jpg
727 ms
bnr_eidai.png
1040 ms
tel_bnr.jpg
1080 ms
index_news_bg.jpg
937 ms
index_news_h3.jpg
987 ms
index_greeting.png
1168 ms
bnr.png
1502 ms
bnr_02.png
1580 ms
section_bg.jpg
1223 ms
index_new_entry_h3.jpg
1259 ms
10604_1.jpg
1794 ms
12119_1.jpg
1772 ms
14509_1.jpg
2448 ms
15140_1.jpg
3369 ms
15074_1.jpg
3367 ms
index_new_entry_footer_bg.jpg
1775 ms
banner_namas.jpg
1942 ms
banner_url.jpg
1972 ms
banner_study.jpg
1938 ms
pms5001-logo_side.jpg
2085 ms
footer_li_bg.png
2114 ms
__utm.gif
13 ms
tiny.css
2081 ms
ee-tera.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
<object> elements do not have alternate text
ee-tera.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
ee-tera.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document uses plugins
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ee-tera.com 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 Ee-tera.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.
ee-tera.com
Open Graph description is not detected on the main page of Ee Tera. 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: