11.3 sec in total
2.1 sec
8.1 sec
997 ms
Click here to check amazing Enz 0 content for Japan. Otherwise, check out these important facts you probably never knew about enz0.net
このサイトについて 個人的に気になった事や覚えておきたい事を書き殴っています。 一人でも良いから同じような事で躓いている人の助けになれば嬉しいなぁ・・・っていうニッチな「なんちゃって技術系ブログ(笑)
Visit enz0.netWe analyzed Enz0.net page load time and found that the first response time was 2.1 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
enz0.net performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value8.9 s
1/100
25%
Value10.4 s
8/100
10%
Value1,780 ms
10/100
30%
Value0.055
98/100
15%
Value16.9 s
5/100
10%
2140 ms
403 ms
433 ms
441 ms
444 ms
Our browser made a total of 148 requests to load all elements on the main page. We found that 41% of them (61 requests) were addressed to the original Enz0.net, 8% (12 requests) were made to Apis.google.com and 4% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Enz0.net.
Page size can be reduced by 1.0 MB (31%)
3.2 MB
2.2 MB
In fact, the total size of Enz0.net main page is 3.2 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. 80% 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 2.0 MB which makes up the majority of the site volume.
Potential reduce by 117.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 117.9 kB or 83% of the original size.
Potential reduce by 108.0 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. Enz 0 images are well optimized though.
Potential reduce by 332.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 332.4 kB or 61% of the original size.
Potential reduce by 443.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. Enz0.net needs all CSS files to be minified and compressed as it can save up to 443.3 kB or 88% of the original size.
Number of requests can be reduced by 70 (50%)
139
69
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enz 0. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
enz0.net
2140 ms
wp-emoji-release.min.js
403 ms
widget.css
433 ms
crayon.min.css
441 ms
classic.css
444 ms
monaco.css
448 ms
font-awesome.min.css
458 ms
bootstrap.css
868 ms
front.css
639 ms
css
89 ms
wpp.css
653 ms
style.css
653 ms
jetpack.css
662 ms
jquery.min.js
122 ms
crayon.min.js
668 ms
bootstrap.min.js
890 ms
front.js
1675 ms
chosen.jquery.min.js
2080 ms
modernizr.custom.min.js
1923 ms
loader.js
259 ms
vertical.css
928 ms
analytics.tag.php
1092 ms
brand
72 ms
adsbygoogle.js
70 ms
ads.js
434 ms
brand
202 ms
plusone.js
276 ms
rakuten_widget.js
2548 ms
jquery.form.min.js
944 ms
noteit.js
293 ms
bookmark_button.js
407 ms
devicepx-jetpack.js
99 ms
gprofiles.js
150 ms
wpgroho.js
971 ms
scripts.js
1101 ms
jquery.slicknav.min.js
1119 ms
wp-embed.min.js
1168 ms
e-201614.js
100 ms
css
268 ms
logo.png
263 ms
ssimg4338160502_01.jpg
892 ms
ssimg4536120102_01.jpg
719 ms
ssimg0326050402_01-300x300.png
891 ms
post_eyecache-1.jpg
294 ms
post_eyecache.jpg
957 ms
eye_catch.png
1784 ms
memo_eye-300x300.jpg
717 ms
20151217_165053_eye.jpg
1875 ms
H_6Bders.jpg
956 ms
ssimage_09.jpg
1783 ms
ssimage_94.jpg
1823 ms
eye.png
3711 ms
post_eyecache.jpg
1873 ms
ssimage_27-300x300.png
1877 ms
ssimage_26-300x300.png
1878 ms
post_eyecache1.jpg
1992 ms
post_eyecache.jpg
1903 ms
ps3-300x300.jpg
1989 ms
post_eyecache.jpg
1898 ms
eys.jpg
1898 ms
post_eyecache1.jpg
1946 ms
post_eyecache.jpg
1947 ms
profile64.png
1987 ms
ssimg4338160502_01-100x100.jpg
2004 ms
ssimg4536120102_01-100x100.jpg
2004 ms
ssimg0326050402_01-100x100.png
2169 ms
post_eyecache-1-100x100.jpg
2166 ms
post_eyecache-100x100.jpg
2216 ms
4368-featured-95x95.jpg
2210 ms
4884-featured-95x95.png
2210 ms
4628-featured-95x95.png
2532 ms
4701-featured-95x95.jpg
2533 ms
4272-featured-95x95.png
2535 ms
gtm.js
216 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
248 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
329 ms
enz0.ttf
2450 ms
google_custom_search_watermark.gif
321 ms
ca-pub-4244574513309981.js
368 ms
zrt_lookup.html
357 ms
show_ads_impl.js
284 ms
adcore.js
122 ms
adcore_pc.js
205 ms
adcore_pc_inline.js
147 ms
ads
324 ms
osd.js
130 ms
ad_spot.aspx
1437 ms
buttons.png
1948 ms
monaco-webfont.woff
2263 ms
ads
286 ms
widgets.js
137 ms
cb=gapi.loaded_0
121 ms
12568944881702074267
147 ms
abg.js
180 ms
m_js_controller.js
903 ms
googlelogo_color_112x36dp.png
142 ms
mtwidget04.affiliate.rakuten.co.jp
912 ms
s
751 ms
x_button_blue2.png
748 ms
hovercard.css
382 ms
services.css
382 ms
button.71000885400e222c3c0eec823f8f93f0.js
247 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
268 ms
cb=gapi.loaded_1
185 ms
cb=gapi.loaded_2
185 ms
badge
371 ms
favicon
334 ms
mobile_unified_button_icon_white.png
189 ms
g.gif
151 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
63 ms
pc_pcview_all.css
331 ms
front_merged.js
425 ms
style.css
271 ms
ad_creative.ashx
1035 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
869 ms
getMWConf.php
575 ms
postmessageRelay
149 ms
syndication
500 ms
255502487514128384
783 ms
follow_button.fd774b599f565016d763dd860cb31c79.ja.html
60 ms
1077434459-postmessagerelay.js
667 ms
rpc:shindig_random.js
90 ms
rs=AGLTcCOPX8tJg-T7WFvDinb1bIZq8Uhccw
50 ms
rs=AGLTcCP9IczaT7Rf-UGgqDPBu0TrwouL5A
83 ms
rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw
278 ms
photo.jpg
778 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
1026 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
1121 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
1424 ms
loading.gif
134 ms
buttons.gif
257 ms
rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw
427 ms
cb=gapi.loaded_0
140 ms
ec1112-06a.jpg
523 ms
4980673001282.jpg
757 ms
imgrc0065754902.jpg
432 ms
clv20160218-2baisyo.jpg
932 ms
rs=AGLTcCOFj8J56TAcea0tDz388X0QgBENFw
318 ms
proxy.jpg
727 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
333 ms
timeline.f7130f11be9c2719286897ede16853b9.dark.ltr.css
131 ms
proxy.jpg
419 ms
activeview
47 ms
IBElIIvF_normal.png
501 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
399 ms
syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css
434 ms
RestoreXidToMediaStorage.html
316 ms
ui
154 ms
enz0.net 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Form elements do not have associated labels
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
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.
enz0.net 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
Page has valid source maps
enz0.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 Enz0.net 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 Enz0.net 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.
enz0.net
Open Graph data is detected on the main page of Enz 0. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: