21.3 sec in total
1.7 sec
16.6 sec
3 sec
Click here to check amazing Evacollector content for Japan. Otherwise, check out these important facts you probably never knew about evacollector.com
『エヴァンゲリオン』関連商品を集めてもうすぐ30年。エヴァグッズの紹介サイトです。
Visit evacollector.comWe analyzed Evacollector.com page load time and found that the first response time was 1.7 sec and then it took 19.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
evacollector.com performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value9.8 s
0/100
25%
Value6.7 s
36/100
10%
Value1,080 ms
24/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
1672 ms
217 ms
402 ms
402 ms
418 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 48% of them (62 requests) were addressed to the original Evacollector.com, 5% (7 requests) were made to Cs.gssprt.jp and 5% (6 requests) were made to Adm.shinobi.jp. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Js.gsspcln.jp.
Page size can be reduced by 389.6 kB (45%)
859.4 kB
469.8 kB
In fact, the total size of Evacollector.com main page is 859.4 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. 40% of websites need less resources to load. Javascripts take 360.8 kB which makes up the majority of the site volume.
Potential reduce by 70.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 70.9 kB or 82% of the original size.
Potential reduce by 6.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. Evacollector images are well optimized though.
Potential reduce by 225.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 225.4 kB or 62% of the original size.
Potential reduce by 87.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. Evacollector.com needs all CSS files to be minified and compressed as it can save up to 87.0 kB or 84% of the original size.
Number of requests can be reduced by 73 (61%)
120
47
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Evacollector. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
evacollector.com
1672 ms
common.css
217 ms
layout.css
402 ms
design.css
402 ms
mobile.css
418 ms
mobile_layout.css
426 ms
advanced.css
444 ms
style.css
489 ms
screen.min.css
593 ms
arpw-frontend.css
608 ms
wpp.css
626 ms
amazonjs.css
637 ms
jquery.js
903 ms
jquery-migrate.min.js
662 ms
counter.css
791 ms
loader.js
334 ms
cfe14a34a18dd52e930cd24825527c18
639 ms
front.min.js
1633 ms
utility.js
819 ms
socialButton.js
844 ms
wp-embed.min.js
1662 ms
wp-emoji-release.min.js
731 ms
analytics.js
249 ms
bgt
2397 ms
0.gif
487 ms
bgt
2531 ms
0.gif
483 ms
bgt
1811 ms
0.gif
512 ms
bg-dot.png
1062 ms
g6409.jpg
1558 ms
icon-gnav.png
340 ms
s-4234234215235423-160x160.jpg
337 ms
s-R1018653-1-160x160.jpg
467 ms
53452342342341-160x160.jpg
511 ms
s-R1018653-160x160.jpg
1046 ms
s-R1018642-160x160.jpg
1048 ms
s-R1018622-160x160.jpg
1203 ms
623654325324-160x160.jpg
1955 ms
cdbb3f8a2c06a8e7c6e4246d2ba54523-160x160.jpg
1058 ms
s-R1018613-160x160.jpg
1059 ms
s-R1018607-160x160.jpg
1808 ms
s-R1018595-160x160.jpg
1453 ms
s-R1018590-160x160.jpg
1889 ms
s-87645356798-160x160.jpg
1447 ms
78797653424567534-160x160.jpg
1777 ms
s-o0500069413601076256-160x160.jpg
1611 ms
2345ytt-160x160.jpg
1788 ms
5435322353452342-160x160.jpg
2134 ms
8449-featured-100x100.jpg
1951 ms
7-featured-100x100.jpg
1959 ms
472-featured-100x100.jpg
1964 ms
1501-featured-100x100.jpg
2070 ms
10200-featured-100x100.jpg
2147 ms
52512451-100x100.jpg
2147 ms
623654325324-100x100.jpg
2547 ms
s-150723_s21-100x100.jpg
2183 ms
s-5324525252-100x100.jpg
2286 ms
s-R1018361-100x100.jpg
3217 ms
s-4234234215235423-150x150.jpg
2342 ms
s-R1018653-1-150x150.jpg
2321 ms
53452342342341-150x150.jpg
2247 ms
s-R1018653-150x150.jpg
2370 ms
collect
57 ms
s-R1018642-150x150.jpg
2222 ms
icon-arrow_r.png
2245 ms
collect
657 ms
1.0.1.js
670 ms
icon-menu02.png
2171 ms
bg-footer-h3.gif
2248 ms
icon-arrow02.png
2133 ms
widgets.js
678 ms
platform.js
435 ms
sdk.js
320 ms
icon-arrow03.png
1764 ms
bg-pagetop.gif
1757 ms
1.0.0.js
174 ms
294 ms
xd_arbiter.php
134 ms
xd_arbiter.php
300 ms
sync
265 ms
cfe14a34a18dd52e930cd24825527c18
376 ms
sync
396 ms
sync
585 ms
push_sync
395 ms
js1
607 ms
ib
224 ms
1.1.0.js
198 ms
cookiesync
219 ms
sync
239 ms
receive_sync
192 ms
js
587 ms
jstag
446 ms
print.css
212 ms
acj
98 ms
ri
211 ms
imp
260 ms
a1033892.js
3534 ms
sync
63 ms
jsk
484 ms
ads.js
154 ms
gl0
226 ms
adcomp_pc.js
61 ms
sspcore_spot.js
166 ms
ssp_spot.ashx
542 ms
sync
397 ms
push_sync
198 ms
cs
257 ms
acs
221 ms
acs
418 ms
cs
224 ms
acs
245 ms
pixel
127 ms
527 ms
gcs
444 ms
sync
80 ms
pixel
68 ms
cs
233 ms
cs
241 ms
cs
223 ms
adcore.js
85 ms
adcore_pc.js
151 ms
cs
180 ms
adcore_pc_inline.js
55 ms
ad_spot.aspx
401 ms
cs
190 ms
style.css
199 ms
ad_creative.ashx
103 ms
defaultAd.gif
402 ms
bd
107 ms
evacollector.com 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.
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
Links do not have a discernible name
evacollector.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
evacollector.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Evacollector.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 Evacollector.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.
evacollector.com
Open Graph description is not detected on the main page of Evacollector. 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: