6.6 sec in total
1.4 sec
4.8 sec
304 ms
Click here to check amazing Dajare content for Japan. Otherwise, check out these important facts you probably never knew about dajare.jp
面白いダジャレやオヤジギャグばかりを集めた、ダジャレのコミュニティーサイト。ダジャレの投稿やランキングも楽しめる!
Visit dajare.jpWe analyzed Dajare.jp page load time and found that the first response time was 1.4 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dajare.jp performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value49.8 s
0/100
25%
Value8.3 s
19/100
10%
Value3,360 ms
2/100
30%
Value0
100/100
15%
Value51.1 s
0/100
10%
1430 ms
308 ms
313 ms
314 ms
363 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 78% of them (64 requests) were addressed to the original Dajare.jp, 5% (4 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Dajare.jp.
Page size can be reduced by 312.7 kB (59%)
529.3 kB
216.7 kB
In fact, the total size of Dajare.jp main page is 529.3 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. Javascripts take 233.3 kB which makes up the majority of the site volume.
Potential reduce by 95.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 95.7 kB or 85% of the original size.
Potential reduce by 38.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. Obviously, Dajare needs image optimization as it can save up to 38.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 160.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 160.4 kB or 69% of the original size.
Potential reduce by 18.2 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. Dajare.jp needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 77% of the original size.
Number of requests can be reduced by 42 (53%)
80
38
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dajare. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
dajare.jp
1430 ms
Common.css
308 ms
Window.js
313 ms
XmlHttpObject.js
314 ms
Text.js
363 ms
File.js
394 ms
Form.js
597 ms
Image.js
615 ms
Opacity.js
664 ms
Event.js
706 ms
Dom.js
787 ms
Style.js
919 ms
jquery-1.11.3.min.js
1581 ms
jquery.bxslider.js
1244 ms
jquery.bxslider.css
1100 ms
jquery.colorbox.1.6.3.min.js
1128 ms
colorbox.css
1132 ms
ajaxzip3.js
23 ms
common.js
1259 ms
js
54 ms
style.css
1297 ms
Layout.css
1135 ms
Text.css
1185 ms
Anchor.css
1299 ms
List.css
1333 ms
Calendar.css
1480 ms
Tab.css
1490 ms
Image.css
1540 ms
Form.css
1670 ms
Print.css
1659 ms
analytics.js
74 ms
Kaibun180x28.png
561 ms
Background.png
181 ms
Logo.png
307 ms
Home.png
308 ms
New.png
360 ms
Ranking.png
357 ms
Vote.png
426 ms
Parts.png
486 ms
Link.png
617 ms
Twitter.png
701 ms
Smart.png
710 ms
Search.png
898 ms
Search.png
700 ms
Category.png
829 ms
Category.png
972 ms
Dajare180x28.png
990 ms
Twitter.png
1053 ms
Twitter.png
1094 ms
Facebook.gif
1172 ms
Google.png
1291 ms
Yahoo.gif
1277 ms
Hatena.png
1298 ms
LiveDoor.gif
1345 ms
Delicious.gif
1436 ms
Ameblo.gif
1530 ms
Background.png
1581 ms
Search.png
1595 ms
New.png
1607 ms
RSS20.png
1686 ms
RankingScore.png
1777 ms
RankingAuthorVote.png
1889 ms
RankingAuthorEvaluation.png
1900 ms
Tag.png
1921 ms
Mobile.png
1962 ms
Mobile.png
2045 ms
Link.png
2133 ms
widgets.js
25 ms
collect
19 ms
collect
89 ms
overlay.png
2151 ms
like.php
182 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
36 ms
syndication
115 ms
657381353105719296
176 ms
ga-audiences
51 ms
vpc6VNjRPXV.js
290 ms
LVx-xkvaJ0b.png
323 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
8 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
14 ms
Icon_normal.png
133 ms
jot
26 ms
dajare.jp accessibility score
dajare.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
dajare.jp 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 Dajare.jp 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 Dajare.jp 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.
dajare.jp
Open Graph description is not detected on the main page of Dajare. 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: