8.9 sec in total
700 ms
8 sec
194 ms
Visit dokosa.com now to see the best up-to-date Dokosa content and also check out these interesting facts you probably never knew about dokosa.com
ディレクトリー型総合検索エンジンです。どんどん登録おねがいします。
Visit dokosa.comWe analyzed Dokosa.com page load time and found that the first response time was 700 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dokosa.com performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value4.5 s
36/100
25%
Value7.6 s
26/100
10%
Value90 ms
98/100
30%
Value0.002
100/100
15%
Value12.0 s
16/100
10%
700 ms
535 ms
742 ms
1216 ms
369 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 11% of them (8 requests) were addressed to the original Dokosa.com, 8% (6 requests) were made to Adm.shinobi.jp and 7% (5 requests) were made to Spdeliver.i-mobile.co.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Sun.d-064.com.
Page size can be reduced by 42.3 kB (41%)
103.0 kB
60.7 kB
In fact, the total size of Dokosa.com main page is 103.0 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. 15% of websites need less resources to load. Javascripts take 38.6 kB which makes up the majority of the site volume.
Potential reduce by 26.6 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 26.6 kB or 78% of the original size.
Potential reduce by 0 B
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. Dokosa images are well optimized though.
Potential reduce by 11.1 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 11.1 kB or 29% of the original size.
Potential reduce by 4.7 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. Dokosa.com needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 84% of the original size.
Number of requests can be reduced by 46 (71%)
65
19
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dokosa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
dokosa.com
700 ms
NewScript
535 ms
load_js.php
742 ms
bgt
1216 ms
0.gif
369 ms
2390109
1076 ms
Brown_bg_1.gif
333 ms
dokodemo.gif
361 ms
fcount.cgi
473 ms
fcount.cgi
464 ms
fcount.cgi
487 ms
bgt
994 ms
0.gif
364 ms
bgt
923 ms
0.gif
395 ms
0.gif
301 ms
0.gif
991 ms
0.gif
387 ms
radial02_red.gif
382 ms
0.gif
391 ms
0.gif
366 ms
0.gif
389 ms
0.gif
375 ms
0.gif
296 ms
0.gif
295 ms
0.gif
303 ms
bgt
1076 ms
0.gif
423 ms
0db0b86b3923c90802b809a1d71c9883
545 ms
twitterlogo.gif
349 ms
bgt
1067 ms
0.gif
444 ms
512 ms
NewReceive
351 ms
08-ok.gif
1279 ms
htmlbanner
354 ms
ad_1_left_0.gif
521 ms
1.0.1.js
335 ms
56.gif
352 ms
1.0.0.js
181 ms
sync
181 ms
0db0b86b3923c90802b809a1d71c9883
259 ms
sync
341 ms
sync
504 ms
push_sync
298 ms
js1
520 ms
ib
188 ms
1.1.0.js
168 ms
cookiesync
188 ms
sync
190 ms
receive_sync
151 ms
js
471 ms
sh.adingo.jp
378 ms
show.php
388 ms
sync
736 ms
push_sync
609 ms
cm
374 ms
ads.js
206 ms
i.adingo.jp
366 ms
adcomp_pc.js
3 ms
sspcore_spot.js
179 ms
ssp_spot.ashx
456 ms
615 ms
624 ms
622 ms
adcore.js
3 ms
adcore_pc.js
5 ms
adcore_pc_inline.js
4 ms
ad_spot.aspx
531 ms
style.css
171 ms
ad_creative.ashx
187 ms
dokosa.com accessibility score
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
dokosa.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
dokosa.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dokosa.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 Dokosa.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
dokosa.com
Open Graph description is not detected on the main page of Dokosa. 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: