10.2 sec in total
1.7 sec
8 sec
527 ms
Click here to check amazing Totoneko content for Japan. Otherwise, check out these important facts you probably never knew about totoneko.com
ゲームの攻略やニュース、セール情報などをお届けします
Visit totoneko.comWe analyzed Totoneko.com page load time and found that the first response time was 1.7 sec and then it took 8.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.
totoneko.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.3 s
10/100
25%
Value9.8 s
10/100
10%
Value1,750 ms
10/100
30%
Value0.098
90/100
15%
Value13.9 s
10/100
10%
1675 ms
366 ms
742 ms
376 ms
382 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 39% of them (59 requests) were addressed to the original Totoneko.com, 5% (8 requests) were made to Ecx.images-amazon.com and 5% (8 requests) were made to Ums.adtechus.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Totoneko.com.
Page size can be reduced by 709.8 kB (50%)
1.4 MB
720.4 kB
In fact, the total size of Totoneko.com main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 653.4 kB which makes up the majority of the site volume.
Potential reduce by 58.8 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 58.8 kB or 81% of the original size.
Potential reduce by 18.5 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. Totoneko images are well optimized though.
Potential reduce by 398.3 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 398.3 kB or 61% of the original size.
Potential reduce by 234.1 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. Totoneko.com needs all CSS files to be minified and compressed as it can save up to 234.1 kB or 84% of the original size.
Number of requests can be reduced by 97 (68%)
143
46
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Totoneko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
totoneko.com
1675 ms
style.css
366 ms
font-awesome.min.css
742 ms
style.css
376 ms
extension.css
382 ms
responsive-pc.css
393 ms
style.css
548 ms
thread-simple.css
561 ms
styles.css
386 ms
sb-type-std.css
603 ms
sb-type-fb.css
725 ms
sb-type-fb-flat.css
749 ms
sb-type-ln.css
773 ms
sb-type-ln-flat.css
933 ms
sb-type-pink.css
765 ms
sb-type-rtail.css
1004 ms
sb-type-drop.css
1087 ms
sb-type-think.css
1122 ms
sb-no-br.css
960 ms
style.css
1589 ms
wpp.css
1123 ms
responsive.dataTables.min.css
1156 ms
tablepress-combined.min.css
1404 ms
font-awesome.min.css
1631 ms
tablepress-responsive-flip.min.css
1308 ms
jquery.js
2897 ms
jquery-migrate.min.js
1542 ms
style.css
1495 ms
style.css
2656 ms
adsbygoogle.js
10 ms
7be96f6f9a8c6e575df2ca8c322874f6
348 ms
5822977087d4067879564a8f260a4b68
361 ms
javascript.js
1897 ms
javascript.js
1172 ms
jquery.form.min.js
1215 ms
scripts.js
1611 ms
jquery.rwdImageMaps.min.js
1369 ms
masonry.min.js
1610 ms
jquery.masonry.min.js
1567 ms
rsvp.js
1767 ms
wp-embed.min.js
1810 ms
wp-emoji-release.min.js
1008 ms
analytics.js
7 ms
linkid.js
53 ms
51HTFKH6QoL._SS300_.jpg
50 ms
banner.blog.with2.net
851 ms
totoneko_title-e1442568101115.png
1221 ms
s_20160319-7-150x150.jpg
221 ms
s_20160316-3-150x150.jpg
397 ms
kagura-150x150.jpg
424 ms
s_20160312-4-150x150.jpg
397 ms
61qRBD44EAL._SL160_-150x147.jpg
806 ms
s_Assault-Android-Cactus1-min-150x150.jpg
1013 ms
s_bismarck-min-150x150.jpg
805 ms
s_2016-03-05-3-150x150.jpg
840 ms
s_Exist-Archive_20151231190626-100x100.jpg
1012 ms
s_2016-02-25-155332-100x100.jpg
1013 ms
s_2016-02-20-143155-100x100.jpg
1253 ms
s_2016-02-20-142819-100x100.jpg
1332 ms
s_2016-02-22-175040-100x100.jpg
1302 ms
51UVoOjB7XL-211x300.jpg
1742 ms
61Nuj70HdCL._SX250_.jpg
38 ms
51zoRNqX6TL._SX250_.jpg
40 ms
61uDu7-Tk3L._SX250_.jpg
37 ms
51ZEwt15hCL._SX250_.jpg
37 ms
518wtGVcmlL._SX250_.jpg
38 ms
51jdfeYlzZL._SX250_.jpg
34 ms
51J54hmQ3mL._SX250_.jpg
38 ms
icomoon.woff
1357 ms
fontawesome-webfont.woff
2196 ms
fontawesome-webfont.woff
3380 ms
collect
72 ms
collect
194 ms
ca-pub-9663805560999360.js
62 ms
zrt_lookup.html
132 ms
show_ads_impl.js
73 ms
ads
378 ms
osd.js
37 ms
ads
341 ms
sdk.js
36 ms
ads
289 ms
ajax-loader.gif
1132 ms
121 ms
xd_arbiter.php
19 ms
xd_arbiter.php
34 ms
1.0.1.js
506 ms
m_js_controller.js
33 ms
abg.js
65 ms
favicon
107 ms
googlelogo_color_112x36dp.png
85 ms
nessie_icon_tiamat_white.png
65 ms
s
51 ms
x_button_blue2.png
7 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
16 ms
1.0.0.js
155 ms
sync
209 ms
7be96f6f9a8c6e575df2ca8c322874f6
198 ms
sync
389 ms
sync
602 ms
push_sync
300 ms
js1
553 ms
ib
180 ms
1.1.0.js
155 ms
activeview
16 ms
cookiesync
180 ms
receive_sync
150 ms
sync
174 ms
js
483 ms
jstag
18 ms
i.js
85 ms
acj
61 ms
js
40 ms
ri
99 ms
rc
162 ms
js
99 ms
aceUAC.js
12 ms
28 ms
generic
17 ms
sync
19 ms
pixel
23 ms
adcount%7C2.0%7C9932%7C3462792%7C0%7C170%7CAdId=6389411;BnId=1;ct=115422056;st=156222;adcid=1;itime=437864336;reqtype=5;;
14 ms
dref=http%253A%252F%252Fadm.shinobi.jp%252Fa%252F7be96f6f9a8c6e575df2ca8c322874f6%253Fx%253D1075%2526y%253D3627%2526url%253Dhttp%25253A%25252F%25252Ftotoneko.com%25252F%2526referrer%253D%2526amoad%253D0%2526user_id%253D%2526du%253Dhttp%25253A%25252F%25252Ftotoneko.com%25252F%2526iw%253D1680%2526ih%253D1050
22 ms
generic
7 ms
0.gif
194 ms
mapuser
8 ms
mapuser
8 ms
providerid=1037;userid=14682c97-704e-4e6b-9f3b-4753353534aa
7 ms
mapuser
9 ms
mapuser
8 ms
mapuser
4 ms
dref=http%253A%252F%252Fadm.shinobi.jp%252Fa%252F7be96f6f9a8c6e575df2ca8c322874f6%253Fx%253D1075%2526y%253D3627%2526url%253Dhttp%25253A%25252F%25252Ftotoneko.com%25252F%2526referrer%253D%2526amoad%253D0%2526user_id%253D%2526du%253Dhttp%25253A%25252F%25252Ftotoneko.com%25252F%2526iw%253D1680%2526ih%253D1050
11 ms
CSG_TWW_MKT_20080513_01%20_photo_300x250.jpg
9 ms
moatad.js
9 ms
n.js
20 ms
usermatch
22 ms
mapuser
19 ms
usermatch
16 ms
Vu3.6cAoJVUAAZtoTJsAAAAw%26626
56 ms
mapuser
6 ms
pixel.htm
49 ms
rum
13 ms
rum
9 ms
rum
13 ms
rum
22 ms
crum
10 ms
ddc.htm
19 ms
rum
19 ms
rum
14 ms
cs.ashx
10 ms
beacon.js
3 ms
print.css
541 ms
bd
33 ms
totoneko.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
totoneko.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
totoneko.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
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 Totoneko.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 Totoneko.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.
totoneko.com
Open Graph description is not detected on the main page of Totoneko. 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: