3.1 sec in total
760 ms
2.2 sec
142 ms
Click here to check amazing Otakuma content for Japan. Otherwise, check out these important facts you probably never knew about otakuma.net
オタク(Otaku)ソーシャルマッチングサービス『おたくま』!!オタクとおたくをマッチングさせる、自動オタク検索システムであなたぴったりな同志がみつかるはず!ソーシャルネットワークサービス(SNS)の1歩先を行く次世代のオタク(Otaku)コミニケーションツール!!
Visit otakuma.netWe analyzed Otakuma.net page load time and found that the first response time was 760 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
otakuma.net performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value3.3 s
69/100
25%
Value3.1 s
93/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value3.1 s
95/100
10%
760 ms
340 ms
555 ms
511 ms
192 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 51% of them (25 requests) were addressed to the original Otakuma.net, 20% (10 requests) were made to Pbs.twimg.com and 8% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (901 ms) belongs to the original domain Otakuma.net.
Page size can be reduced by 44.2 kB (7%)
660.9 kB
616.6 kB
In fact, the total size of Otakuma.net main page is 660.9 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. 40% of websites need less resources to load. Images take 584.2 kB which makes up the majority of the site volume.
Potential reduce by 6.7 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 6.7 kB or 65% of the original size.
Potential reduce by 1.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. Otakuma images are well optimized though.
Potential reduce by 24.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 24.2 kB or 47% of the original size.
Potential reduce by 11.9 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. Otakuma.net needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 81% of the original size.
Number of requests can be reduced by 20 (42%)
48
28
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otakuma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
otakuma.net
760 ms
base.css
340 ms
SpryTabbedPanels2.js
555 ms
AdLantisLoader.js
511 ms
new_main.css
192 ms
SpryTabbedPanels2.css
171 ms
twitter.css
340 ms
body_bg.gif
193 ms
bg.gif
173 ms
logo.gif
187 ms
head.jpg
506 ms
head_menu01.jpg
677 ms
spacer.gif
366 ms
body_contents_bg.gif
374 ms
body_contents_top.gif
373 ms
body_contents_footer.gif
398 ms
body_contents_top2.gif
545 ms
01.jpg
558 ms
02.jpg
741 ms
03.jpg
569 ms
04.jpg
675 ms
05.jpg
901 ms
06.jpg
742 ms
news_title.gif
758 ms
twitter_li.gif
841 ms
widgets.js
4 ms
foot.jpg
827 ms
ga.js
28 ms
adlantis.www.js
180 ms
swfobject.js
357 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
22 ms
__utm.gif
11 ms
syndication
86 ms
256797825533362176
162 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
hEwX6D4k_normal.png
55 ms
CcbncuIUAAAyM4t.jpg:large
123 ms
CcbaXGhVAAEcqf7.jpg
58 ms
CcX4HFFUUAAyPqW.jpg
110 ms
CcWbV6_UMAAbazt.jpg
56 ms
CcRxkiYVAAAbsGh.jpg:large
105 ms
CcRnMpPUEAAWOv8.jpg:large
101 ms
CcRliSqUEAA4zlp.jpg
59 ms
CcNszEgUEAAdsOP.jpg:large
58 ms
CcNnfSiUMAA5Toc.jpg
98 ms
load_script
359 ms
load_script
396 ms
jot
26 ms
otakuma.net accessibility score
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
otakuma.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
otakuma.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otakuma.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 Otakuma.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.
otakuma.net
Open Graph description is not detected on the main page of Otakuma. 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: