8.5 sec in total
928 ms
5.8 sec
1.7 sec
Visit donpy.net now to see the best up-to-date Donpy content for Japan and also check out these interesting facts you probably never knew about donpy.net
@donpy のハマりもの紹介ブログ Ver.10.1
Visit donpy.netWe analyzed Donpy.net page load time and found that the first response time was 928 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
donpy.net performance score
name
value
score
weighting
Value11.8 s
0/100
10%
Value16.3 s
0/100
25%
Value26.9 s
0/100
10%
Value760 ms
39/100
30%
Value0.003
100/100
15%
Value12.9 s
13/100
10%
928 ms
334 ms
522 ms
26 ms
337 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 26% of them (30 requests) were addressed to the original Donpy.net, 9% (10 requests) were made to Apis.google.com and 8% (9 requests) were made to B.hatena.ne.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Donpy.net.
Page size can be reduced by 464.5 kB (44%)
1.1 MB
590.9 kB
In fact, the total size of Donpy.net main page is 1.1 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. Javascripts take 429.9 kB which makes up the majority of the site volume.
Potential reduce by 63.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 63.9 kB or 79% of the original size.
Potential reduce by 18.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. Donpy images are well optimized though.
Potential reduce by 225.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 225.2 kB or 52% of the original size.
Potential reduce by 157.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. Donpy.net needs all CSS files to be minified and compressed as it can save up to 157.0 kB or 83% of the original size.
Number of requests can be reduced by 71 (64%)
111
40
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Donpy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.donpy.net
928 ms
normalize.css
334 ms
style.css
522 ms
font-awesome.css
26 ms
crayon.min.css
337 ms
styles.css
344 ms
fi-buttons.css
369 ms
jetpack.css
644 ms
jquery.min.js
30 ms
crayon.min.js
680 ms
widgets.js
10 ms
plusone.js
112 ms
bookmark_button.js
678 ms
adsbygoogle.js
62 ms
widget.js
380 ms
jquery.form.min.js
676 ms
scripts.js
380 ms
devicepx-jetpack.js
8 ms
gprofiles.js
8 ms
wpgroho.js
424 ms
base.js
546 ms
scroll.js
676 ms
e-201607.js
58 ms
js1.php
1198 ms
ga.js
41 ms
wp-emoji-release.min.js
431 ms
__utm.gif
11 ms
feedly-follow-rectangle-flat-medium_2x.png
144 ms
banner_125x35_1.gif
228 ms
tfg.gif
593 ms
1921024_833201500044073_7319623185323773015_o2.jpg
696 ms
IMG_0874-150x150.jpg
415 ms
IMG_9253-150x150.jpg
414 ms
IMG_9275-150x150.jpg
413 ms
DSC_5035-150x150.jpg
256 ms
DSC_5050-150x150.jpg
585 ms
IMG_8447-150x150.jpg
666 ms
101415_015953_AM-150x150.jpg
559 ms
IMG_8426-150x150.png
1091 ms
12088094_1021934007837487_8768645106116075031_n-150x150.jpg
838 ms
001-150x150.png
1289 ms
search.png
838 ms
skitched-20131124-160026.jpg
1241 ms
amnbadge-300c.png
1058 ms
NewImage.png
1057 ms
NewImage124.png
1239 ms
button-only.gif
215 ms
fontawesome-webfont.woff
35 ms
cb=gapi.loaded_0
144 ms
like.php
275 ms
478 ms
475 ms
ca-pub-4458461285170838.js
205 ms
zrt_lookup.html
438 ms
show_ads_impl.js
188 ms
zH0IPw-UmpL.js
814 ms
LVx-xkvaJ0b.png
838 ms
cb=gapi.loaded_1
286 ms
fastbutton
401 ms
ads
484 ms
ads
428 ms
reset.css
45 ms
entry-button.css
43 ms
osd.js
15 ms
widget.css
191 ms
tracking1.html
205 ms
jquery.min.js
496 ms
favicon.gif
416 ms
vbutton-bg.png
95 ms
postmessageRelay
209 ms
cb=gapi.loaded_0
101 ms
cb=gapi.loaded_1
117 ms
rranking.gif
1130 ms
grlryt2bdKIyfMSOhzd1eA.woff
243 ms
head.gif
238 ms
load.gif
658 ms
foot.gif
414 ms
logo.gif
414 ms
analytics.js
88 ms
api.js
159 ms
core:rpc:shindig.random:shindig.sha1.js
285 ms
2536007149-postmessagerelay.js
231 ms
61daaeab.js
1007 ms
collect
73 ms
collect
92 ms
5171746271700867932
254 ms
abg.js
281 ms
m_js_controller.js
314 ms
googlelogo_color_112x36dp.png
524 ms
633 ms
6341327852158743188
287 ms
x_button_blue2.png
182 ms
s
158 ms
-Wxc5n6ag8mSVPmrosQZJ6hEHpQooK3Qr1Gxv0lUkvE.js
7 ms
g.gif
7 ms
b001.gif
189 ms
js2.php
368 ms
trackfeedbargreen.gif
497 ms
hovercard.css
116 ms
services.css
116 ms
button.b059c0eb61ea902a882e5c5b3c66a17a.js
88 ms
json
191 ms
json
242 ms
cb=gapi.loaded_2
68 ms
subscribe_embed
152 ms
activeview
23 ms
tweet_button.baa54ded21a982344c4ced326592f3de.ja.html
24 ms
www-subscribe-embed-vflWJjAep.css
101 ms
photo.jpg
95 ms
www-subscribe-embed.js
127 ms
jot
168 ms
www-hitchhiker-vfluKv9vH.png
48 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_3
11 ms
donpy.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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
donpy.net 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
donpy.net SEO score
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 Donpy.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 Donpy.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.
donpy.net
Open Graph data is detected on the main page of Donpy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: