12.5 sec in total
551 ms
11.5 sec
428 ms
Welcome to holysmoke.jp homepage info - get ready to check Holysmoke best content for Japan right away, or after learning these important things about holysmoke.jp
ロケットフィッシュ、ボンザー、シングルフィン等,70年代スタイルのサーフカルチャーをお届けする神奈川県横浜市ホーリースモーク
Visit holysmoke.jpWe analyzed Holysmoke.jp page load time and found that the first response time was 551 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
holysmoke.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value21.9 s
0/100
25%
Value18.6 s
0/100
10%
Value510 ms
57/100
30%
Value1.266
1/100
15%
Value15.2 s
7/100
10%
551 ms
890 ms
12 ms
362 ms
550 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 89% of them (123 requests) were addressed to the original Holysmoke.jp, 3% (4 requests) were made to Maps.google.com and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Holysmoke.jp.
Page size can be reduced by 517.1 kB (14%)
3.6 MB
3.1 MB
In fact, the total size of Holysmoke.jp main page is 3.6 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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 53.6 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 53.6 kB or 85% of the original size.
Potential reduce by 22.8 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. Holysmoke images are well optimized though.
Potential reduce by 390.1 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 390.1 kB or 69% of the original size.
Potential reduce by 50.7 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. Holysmoke.jp needs all CSS files to be minified and compressed as it can save up to 50.7 kB or 78% of the original size.
Number of requests can be reduced by 49 (36%)
136
87
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Holysmoke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
holysmoke.jp
551 ms
www.holysmoke.jp
890 ms
font-awesome.min.css
12 ms
import.css
362 ms
mt.js
550 ms
cube.site.js
367 ms
cube.win_op.js
375 ms
jquery.min.js
33 ms
jquery.easing.1.3.js
385 ms
jquery.mousewheel.js
587 ms
jquery.rollOver.js
714 ms
jquery.slideImage.js
744 ms
jquery.fullSlide.js
738 ms
jquery.customScroll.js
769 ms
jquery.droppy.js
909 ms
jquery.bxslider.js
1331 ms
fixHeight.js
1069 ms
shadowbox.js
1418 ms
js
27 ms
config.js.php
1098 ms
ga.js
1121 ms
w_js.php
1051 ms
bookmark_button.js
338 ms
base.css
1054 ms
content.css
1104 ms
dmanager.css
1124 ms
shop.css
1268 ms
shop-other.css
1313 ms
shadowbox.css
1392 ms
extra.css
1416 ms
analytics.js
47 ms
bg.jpg
337 ms
logo.jpg
545 ms
hnav01.jpg
376 ms
hnav02.jpg
377 ms
shop-search-btn.jpg
393 ms
shop-cart-btn.jpg
401 ms
gnav01.jpg
670 ms
gnav02.jpg
771 ms
gnav03.jpg
755 ms
gnav04.jpg
765 ms
gnav05.jpg
796 ms
gnav06.jpg
949 ms
data-150813170150.jpg
2990 ms
p2.jpg
1871 ms
p3.jpg
2851 ms
p4.jpg
3138 ms
p5.jpg
3015 ms
p6.jpg
3476 ms
p7.jpg
3987 ms
slideshow-pager.jpg
3196 ms
shop-recommend-title.jpg
3340 ms
02061604_56b59b12e7770_t145x125.jpg
3392 ms
08311716_5402d9c389786_t145x125.jpg
3505 ms
02181641_56c5759cbe40c_t145x125.jpg
3538 ms
01101503_5691f44ef0c2a_t145x125.jpg
3888 ms
11231340_565298a308e85_t145x125.jpg
3732 ms
09101617_55f12e9f7e3be_t145x125.jpg
3816 ms
02191401_56c6a1ad46c5c_t145x125.jpg
3844 ms
09121624_55f3d321bd6c3_t145x125.jpg
4100 ms
02201609_56c8113063600_t145x125.jpg
4093 ms
09100856_4c897441256de_t145x125.jpg
4161 ms
01221459_56a1c52d519cd_t145x125.jpg
4207 ms
10181539_56233e8f42b52_t145x125.jpg
4398 ms
news-title.jpg
4331 ms
2016227141545_224x154.jpg
4444 ms
news-date-bg.png
4443 ms
collect
42 ms
plusone.js
93 ms
widgets.js
16 ms
ga.js
35 ms
__utm.gif
44 ms
cb=gapi.loaded_0
5 ms
2016226145220_224x154.jpg
4203 ms
201622416226_224x154.jpg
4195 ms
2016220164449_224x154.jpg
4323 ms
2016219143319_224x154.jpg
4359 ms
2016218164944_224x154.jpg
4413 ms
201621715440_224x154.jpg
4280 ms
2016214145120_224x154.jpg
4251 ms
2016211145954_224x154.jpg
4166 ms
201628151322_224x154.jpg
4297 ms
201626165614_224x154.jpg
4510 ms
201623155641_224x154.jpg
4381 ms
20162116257_224x154.jpg
4242 ms
2016131151032_224x154.jpg
3411 ms
2016129154415_224x154.jpg
2428 ms
201612716159_224x154.jpg
2424 ms
2016124164219_224x154.jpg
2704 ms
2016122162256_224x154.jpg
2435 ms
2016119185225_224x154.jpg
2427 ms
201611717913_224x154.jpg
2285 ms
2016115162747_224x154.jpg
2259 ms
more.jpg
2297 ms
side-banner01.jpg
2450 ms
side-banner02.jpg
2463 ms
side-banner03.jpg
2270 ms
pagetop.jpg
2182 ms
footer-guide-title.jpg
2221 ms
footer-guide-subtitle01.jpg
2219 ms
footer-guide-subtitle02.jpg
2325 ms
footer-guide-subtitle03.jpg
2252 ms
footer-guide-subtitle04.jpg
2243 ms
footer-guide-subtitle05.jpg
2214 ms
footer-guide-subtitle06.jpg
2190 ms
shop-cat06.jpg
2141 ms
snav-btn-bg.jpg
2252 ms
shop-cat07.jpg
2242 ms
shop-cat01.jpg
2251 ms
shop-cat02.jpg
2208 ms
shop-cat03.jpg
2167 ms
shop-cat04.jpg
2145 ms
shop-cat05.jpg
2250 ms
shop-cat08.jpg
2211 ms
shop-cat09.jpg
2243 ms
shop-cat10.jpg
2170 ms
shop-cat11.jpg
2195 ms
common.js
5 ms
util.js
21 ms
stats.js
20 ms
AuthenticationService.Authenticate
275 ms
fnav-btn-bg.jpg
2167 ms
2187 ms
slideshow-pager-on.jpg
2190 ms
02061604_56b59b12e7770_t145x125.jpg
2146 ms
08311716_5402d9c389786_t145x125.jpg
2174 ms
02181641_56c5759cbe40c_t145x125.jpg
2195 ms
01101503_5691f44ef0c2a_t145x125.jpg
2388 ms
11231340_565298a308e85_t145x125.jpg
2152 ms
09101617_55f12e9f7e3be_t145x125.jpg
2095 ms
02191401_56c6a1ad46c5c_t145x125.jpg
2160 ms
09121624_55f3d321bd6c3_t145x125.jpg
2342 ms
02201609_56c8113063600_t145x125.jpg
2157 ms
09100856_4c897441256de_t145x125.jpg
2297 ms
01221459_56a1c52d519cd_t145x125.jpg
2141 ms
10181539_56233e8f42b52_t145x125.jpg
2392 ms
shop-recomment-prev.jpg
2189 ms
shop-recomment-next.jpg
2232 ms
holysmoke.jp 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.
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
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.
holysmoke.jp 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
Browser errors were logged to the console
holysmoke.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Holysmoke.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 Holysmoke.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.
holysmoke.jp
Open Graph description is not detected on the main page of Holysmoke. 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: