6.7 sec in total
814 ms
5.5 sec
338 ms
Welcome to eczine.jp homepage info - get ready to check ECzine best content for Japan right away, or after learning these important things about eczine.jp
ECを中心にコマース・テクノロジーに関する情報を発信することで、コマースビジネスを支援するメディアです。
Visit eczine.jpWe analyzed Eczine.jp page load time and found that the first response time was 814 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eczine.jp performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value9.6 s
0/100
25%
Value8.5 s
17/100
10%
Value2,440 ms
5/100
30%
Value0.055
98/100
15%
Value15.3 s
7/100
10%
814 ms
877 ms
617 ms
794 ms
362 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 77% of them (60 requests) were addressed to the original Eczine.jp, 9% (7 requests) were made to Tpc.googlesyndication.com and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Eczine.jp.
Page size can be reduced by 631.1 kB (39%)
1.6 MB
1.0 MB
In fact, the total size of Eczine.jp main page is 1.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. 40% of websites need less resources to load. Images take 873.8 kB which makes up the majority of the site volume.
Potential reduce by 182.5 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 182.5 kB or 88% of the original size.
Potential reduce by 41.4 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. ECzine images are well optimized though.
Potential reduce by 251.2 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 251.2 kB or 67% of the original size.
Potential reduce by 156.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. Eczine.jp needs all CSS files to be minified and compressed as it can save up to 156.0 kB or 86% of the original size.
Number of requests can be reduced by 27 (35%)
77
50
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ECzine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
eczine.jp
814 ms
bootstrap.css
877 ms
common.css
617 ms
jquery.min.js
794 ms
jquery.cookie.js
362 ms
jquery.xdomainajax.js
396 ms
respond.min.js
706 ms
std.js
700 ms
dpf.js
750 ms
carousel.js
908 ms
bootstrap.js
1082 ms
function.js
792 ms
smart-crossfade.js
836 ms
adparser.js
1044 ms
gpt.js
5 ms
pubads_impl_81.js
7 ms
container.html
8 ms
non-responsive.css
328 ms
dc.js
59 ms
logo_eczine.png
165 ms
logo_eczine_smp.png
367 ms
btn_nav01_on.png
403 ms
btn_nav05_off.png
404 ms
btn_nav03_off.png
475 ms
btn_nav04_off.png
460 ms
btn_nav02_off.png
512 ms
btn_nav07_off.png
708 ms
360.png
1330 ms
360.png
906 ms
360.png
1156 ms
360.png
936 ms
360.png
1226 ms
360.png
1716 ms
btn_regist_on.png
1215 ms
btn_regist_off.png
1291 ms
btn_login_on.png
1522 ms
btn_login_off.png
1580 ms
logo_shoeisha.png
1588 ms
logo_privacymark.png
1581 ms
sns_google.png
1691 ms
sns_facebook.png
1899 ms
sns_twitter.png
1904 ms
all.js
276 ms
ads
321 ms
__utm.gif
14 ms
155 ms
xd_arbiter.php
242 ms
xd_arbiter.php
445 ms
16885444789871597396
144 ms
sns.png
1562 ms
osd.js
57 ms
pickup.png
1556 ms
icn_set.png
1590 ms
icn_titIcn.png
1651 ms
icon_pr.gif
1799 ms
200.png
1943 ms
200.png
2019 ms
200.png
2039 ms
200.png
1975 ms
200.png
2137 ms
200.png
2496 ms
icn_subLogin.png
2289 ms
17075951306310405343
69 ms
6080168229224492986
42 ms
icn_subRank.png
2253 ms
687904646263442520
18 ms
3992117935257681731
15 ms
11554163725864033798
46 ms
btn_search_off.png
2181 ms
bg_footer.png
2196 ms
btn_pagetop.png
2273 ms
activeview
13 ms
print.css
349 ms
btn_nav05_on.png
299 ms
btn_nav03_on.png
310 ms
btn_nav04_on.png
324 ms
btn_nav02_on.png
349 ms
btn_nav07_on.png
365 ms
eczine.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
eczine.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
eczine.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 Eczine.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 Eczine.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.
eczine.jp
Open Graph data is detected on the main page of ECzine. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: