4.9 sec in total
1.5 sec
3.3 sec
72 ms
Click here to check amazing COOKIEBOY content. Otherwise, check out these important facts you probably never knew about cookieboy.net
2008年より活動をはじめ、アパレルブランドなど様々なエキシビジョンやパーティ用クッキーを手がけながら自身の展示会やワークショップなどでも活動している COOKIEBOY の WEBSITE です。
Visit cookieboy.netWe analyzed Cookieboy.net page load time and found that the first response time was 1.5 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
cookieboy.net performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value4.7 s
33/100
25%
Value8.1 s
21/100
10%
Value260 ms
83/100
30%
Value0
100/100
15%
Value6.4 s
59/100
10%
1529 ms
174 ms
716 ms
514 ms
343 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 88% of them (23 requests) were addressed to the original Cookieboy.net, 8% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Cookieboy.net.
Page size can be reduced by 5.5 kB (1%)
898.6 kB
893.1 kB
In fact, the total size of Cookieboy.net main page is 898.6 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 823.3 kB which makes up the majority of the site volume.
Potential reduce by 5.0 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 5.0 kB or 67% 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. COOKIEBOY images are well optimized though.
Potential reduce by 405 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 105 B
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. Cookieboy.net has all CSS files already compressed.
Number of requests can be reduced by 6 (24%)
25
19
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COOKIEBOY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
cookieboy.net
1529 ms
styles.css
174 ms
minified.css.php
716 ms
jquery.js
514 ms
jquery.form.min.js
343 ms
scripts.js
344 ms
common.js
345 ms
jquery.backstretch.min.js
347 ms
logo.gif
518 ms
nav_news.gif
517 ms
nav_about.gif
545 ms
nav_gallery.gif
527 ms
nav_blog.gif
685 ms
nav_webshop.gif
692 ms
nav_contact.gif
691 ms
0b9068a1bdc224db7ed10c3fce8755d11-292x219.jpg
933 ms
btn_facebook.png
761 ms
btn_twitter.png
858 ms
btn_instagram.png
863 ms
copyright.gif
869 ms
header_bg.gif
206 ms
footer_bg.gif
207 ms
analytics.js
20 ms
main.jpg
960 ms
collect
28 ms
js
66 ms
cookieboy.net 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
cookieboy.net 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
General
Impact
Issue
Detected JavaScript libraries
cookieboy.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Cookieboy.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 Cookieboy.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.
cookieboy.net
Open Graph data is detected on the main page of COOKIEBOY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: