3.6 sec in total
526 ms
3 sec
113 ms
Visit coldrain.jp now to see the best up-to-date Coldrain content for Russia and also check out these interesting facts you probably never knew about coldrain.jp
coldrainオフィシャルサイト、公式グッズ販売、ライブ情報の発信。 coldrain。2007 年名古屋でMasato(Vo)Y.K.C(Gt)Sugi(Gt)RxYxO(Ba)Katsuma(Dr)の5 人で結成。
Visit coldrain.jpWe analyzed Coldrain.jp page load time and found that the first response time was 526 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
coldrain.jp performance score
name
value
score
weighting
Value16.7 s
0/100
10%
Value22.6 s
0/100
25%
Value16.7 s
0/100
10%
Value2,100 ms
7/100
30%
Value0.015
100/100
15%
Value28.4 s
0/100
10%
526 ms
1020 ms
30 ms
203 ms
507 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 27% of them (20 requests) were addressed to the original Coldrain.jp, 26% (19 requests) were made to Encore.scdn.co and 22% (16 requests) were made to Embed-cdn.spotifycdn.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Coldrain.jp.
Page size can be reduced by 246.6 kB (20%)
1.2 MB
993.2 kB
In fact, the total size of Coldrain.jp main page is 1.2 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. Only a small number of websites need less resources to load. Javascripts take 821.3 kB which makes up the majority of the site volume.
Potential reduce by 115.5 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 115.5 kB or 79% 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. Coldrain images are well optimized though.
Potential reduce by 131.0 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 131.0 kB or 16% of the original size.
Potential reduce by 44 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. Coldrain.jp has all CSS files already compressed.
Number of requests can be reduced by 40 (78%)
51
11
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coldrain. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
coldrain.jp
526 ms
coldrain.jp
1020 ms
webfont.js
30 ms
reset.css
203 ms
style.css
507 ms
drawer.min.css
68 ms
5dcc537bc653b816c58d.css
718 ms
polyfills-f28c831decbf144a7cc5.js
725 ms
main-a6e64ebd47c571e990e9.js
722 ms
webpack-50bee04d1dc61f8adf5b.js
724 ms
framework.2e756dc96581c9ba464a.js
722 ms
75fc9c18.b05832cb80ca0878d918.js
724 ms
388db4e54873829912e377368c4cbc0108516f83.37a42c5318c48859516e.js
901 ms
cb66474e78ad0dba396bee8b140ca470735ccec0.fce4cc4ac73e693c4241.js
1063 ms
f9a5c3c4ec3f33e7b18d0ea58a316be2b488e0f7.6d66190da45ac124e73d.js
902 ms
5eacaf93eca2ceede96943d5c8393b7ebdc89166.a86d87878619ab1b82be.js
902 ms
c40705d12f3753665b2482f33001ed75f479ce79.a08459814d2925805296.js
900 ms
71247caf95475e3ea7f9a0f8a30beb258b23d005.2064b705955387ee67d5.js
900 ms
_app-8b9ac39bb61e74ae2275.js
1243 ms
index-6df02204ca3f581b2f02.js
1415 ms
_buildManifest.js
1070 ms
_ssgManifest.js
1069 ms
css
57 ms
eab5e90c-0019-41b9-a478-f271fb0286c3
42 ms
JUHgTYLyYuc
111 ms
4pCVGaLWxDe4d8bsjsnmUM
141 ms
52fe9169-ce06-4b9b-8d13-9783bf3db8eb
47 ms
5120563d-6b22-4418-b102-63df4f1c9ca3
45 ms
ef7fa1bf-5fb4-418e-aa66-4b019a47c071
45 ms
www-player.css
13 ms
www-embed-player.js
32 ms
base.js
60 ms
f4338d83daa9ef42.css
336 ms
97bb7063d29771a1.css
352 ms
3802f0f0fdd596bb.css
357 ms
polyfills-c67a75d1b6f99dc8.js
377 ms
webpack-c6cacb2e73def31f.js
359 ms
framework-ca706bf673a13738.js
372 ms
main-08df201b32607c28.js
372 ms
_app-c48e54fcee0483bd.js
414 ms
fec483df-ed779ce1028b7b0c.js
412 ms
7532-9ada25933e41e6fd.js
405 ms
239-6eb6b98f9c269af8.js
444 ms
7469-90915e1f2a74f8b8.js
414 ms
4836-25a7c767a2648287.js
422 ms
%5Bid%5D-4b5f3caae5092c8c.js
443 ms
_buildManifest.js
453 ms
_ssgManifest.js
454 ms
ad_status.js
241 ms
--9dH29IQ9CksBulhkJupx8P-yH9Jquge0_97VfE0Pw.js
185 ms
embed.js
85 ms
CircularSpTitle-Bold-1624fb2df28c20d7203d7fb86ce8b481.woff
291 ms
CircularSpTitle-Black-506746f387a26f25aa3d023b3e501d34.woff
397 ms
CircularSp-Arab-Book-1cd31794cbdd53724469ba03e8573dba.woff
376 ms
CircularSp-Arab-Bold-47ca0fd648a183136981f28d0218cef6.woff
398 ms
CircularSp-Arab-Black-9dda323448d48d7e6cabf84d2df7dc11.woff
397 ms
CircularSp-Hebr-Book-d8209975eafc81a9499df8401a339ddd.woff
398 ms
CircularSp-Hebr-Bold-caa03e4cb8690e726ef1625c7d91a7a5.woff
397 ms
CircularSp-Hebr-Black-f52613a9d541248805af1d0bb33102f8.woff
402 ms
CircularSp-Cyrl-Book-6f078f781ee313e298ad8997fd1ffe3d.woff
399 ms
CircularSp-Cyrl-Bold-7e54bccaf45728c472079785d5cd4519.woff
399 ms
CircularSp-Cyrl-Black-b4305d9bf82554f631d2636c3ef90c54.woff
400 ms
CircularSp-Grek-Book-c9de2c0741586c1ab7b6e95541fc7807.woff
400 ms
CircularSp-Grek-Bold-53bb923248ba22cf5554bbe5f434c5c8.woff
404 ms
CircularSp-Grek-Black-49883536c1a3bfc688235ce40572731d.woff
401 ms
CircularSp-Deva-Book-e1dc3d746b24723f8d3dadb314b97705.woff
402 ms
CircularSp-Deva-Bold-a218ed3bd8e480245847933a79f4ebfb.woff
401 ms
CircularSp-Deva-Black-f1dca2ee660273063af0316d4b7da438.woff
403 ms
CircularSp-Book-3f73da7d35bd81c706bce7bbb84964de.woff
402 ms
CircularSp-Bold-856afe2da4ba4e61239b129e2c16d633.woff
404 ms
Create
105 ms
id
95 ms
GenerateIT
42 ms
coldrain.jp 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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>).
coldrain.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
Missing source maps for large first-party JavaScript
coldrain.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 Coldrain.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 Coldrain.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.
coldrain.jp
Open Graph data is detected on the main page of Coldrain. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: