5.3 sec in total
959 ms
4.2 sec
169 ms
Visit dake.cc now to see the best up-to-date Dake content and also check out these interesting facts you probably never knew about dake.cc
誕生日プレゼント、プロポーズ、結婚式、結婚記念日のサプライズ演出は、喜ばせ屋。
Visit dake.ccWe analyzed Dake.cc page load time and found that the first response time was 959 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dake.cc performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value12.4 s
0/100
25%
Value10.4 s
8/100
10%
Value4,740 ms
0/100
30%
Value0.264
47/100
15%
Value14.1 s
9/100
10%
959 ms
873 ms
544 ms
557 ms
558 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 90% of them (35 requests) were addressed to the original Dake.cc, 10% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Dake.cc.
Page size can be reduced by 172.5 kB (29%)
595.7 kB
423.2 kB
In fact, the total size of Dake.cc main page is 595.7 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. 20% of websites need less resources to load. Images take 495.9 kB which makes up the majority of the site volume.
Potential reduce by 15.1 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 15.1 kB or 78% of the original size.
Potential reduce by 101.9 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, Dake needs image optimization as it can save up to 101.9 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 55.6 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. Dake.cc needs all CSS files to be minified and compressed as it can save up to 55.6 kB or 88% of the original size.
Number of requests can be reduced by 9 (24%)
37
28
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
dake.cc
959 ms
newhome.css
873 ms
newhome1.css
544 ms
newhome2.css
557 ms
newhome3.css
558 ms
analy2.js
177 ms
ga.js
31 ms
top-titlelogo1.jpg
357 ms
top-line-back.gif
187 ms
top-titlelogo2.jpg
387 ms
top-titlelogo3.jpg
544 ms
main-top-title.jpg
557 ms
omoide.jpg
357 ms
masukomi.jpg
372 ms
main-menu1.jpg
743 ms
main-menu-line.gif
531 ms
main-menu2.jpg
743 ms
main-menu3.jpg
777 ms
main-menu4.jpg
883 ms
main-menu5.jpg
905 ms
main-menu6.jpg
1114 ms
main-menu7.jpg
1270 ms
main-menu8.jpg
1114 ms
main-movie-right1.jpg
1300 ms
main-movie-right2.jpg
1588 ms
yrokobi-top-pp1.jpg
1810 ms
main-movie-bottomright-up.jpg
1670 ms
main-movie-right4.jpg
1855 ms
main-movie-bottomright-bottom.jpg
1621 ms
under-menu-5.jpg
1861 ms
top-leftspace.gif
1765 ms
spacer.gif
1797 ms
movie_banner_01.jpg
2041 ms
movie_banner_02.jpg
2117 ms
movie_banner_03.jpg
2149 ms
img_index_banner.jpg
2714 ms
__utm.gif
14 ms
__utm.gif
11 ms
__utm.gif
20 ms
dake.cc accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
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
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dake.cc 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
dake.cc 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 doesn't use legible font sizes
ZH
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dake.cc can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed Japanese language. Our system also found out that Dake.cc 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.
dake.cc
Open Graph description is not detected on the main page of Dake. 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: