10.1 sec in total
1.5 sec
8.4 sec
197 ms
Visit growly.net now to see the best up-to-date Growly content and also check out these interesting facts you probably never knew about growly.net
GROWLYは、2012/3/19にopenするライブハウスです。京都の音楽シーンを一か所に集め、音楽シーン全体を盛り上げていきます。
Visit growly.netWe analyzed Growly.net page load time and found that the first response time was 1.5 sec and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
growly.net performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value9.9 s
0/100
25%
Value4.7 s
69/100
10%
Value400 ms
67/100
30%
Value0.685
7/100
15%
Value8.8 s
35/100
10%
1468 ms
878 ms
354 ms
706 ms
713 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 54% of them (65 requests) were addressed to the original Growly.net, 25% (30 requests) were made to Pbs.twimg.com and 4% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Growly.net.
Page size can be reduced by 637.0 kB (38%)
1.7 MB
1.1 MB
In fact, the total size of Growly.net main page is 1.7 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. 50% of websites need less resources to load. Images take 847.6 kB which makes up the majority of the site volume.
Potential reduce by 31.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 31.5 kB or 75% of the original size.
Potential reduce by 14.6 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. Growly images are well optimized though.
Potential reduce by 298.3 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 298.3 kB or 66% of the original size.
Potential reduce by 292.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. Growly.net needs all CSS files to be minified and compressed as it can save up to 292.6 kB or 84% of the original size.
Number of requests can be reduced by 41 (35%)
117
76
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Growly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
growly.net
1468 ms
thema.css
878 ms
reset.css
354 ms
common.css
706 ms
page_style.css
713 ms
blog.css
404 ms
calendar.css
709 ms
prettyPhoto.css
1061 ms
jquery.min.js
25 ms
jquery-ui.min.js
39 ms
jquery.biggerlink.js
427 ms
jquery.prettyPhoto.js
1462 ms
jlib.js
903 ms
common.js
1310 ms
image.js
961 ms
jarty.js
1443 ms
upload.js
942 ms
files.js
1355 ms
resize_up_img.js
1350 ms
image_resize.js
1348 ms
public.js
1667 ms
timepicker.js
2282 ms
auto_list.js
1799 ms
image.js
1718 ms
logo_growly.gif
1774 ms
navi_schedule_off.gif
1658 ms
navi_information_off.gif
1772 ms
navi_tv_off.gif
1772 ms
navi_contact_off.gif
1723 ms
top_title_twitter.gif
2135 ms
top_title_blog.gif
2283 ms
top_btn_more.gif
2283 ms
82fb665f35122b4f6f5423c07d59ccb1133858e260x.jpg
2591 ms
e3165edaf816fd94ed9c4e6687196bd7537688e260x.jpg
3345 ms
d56cc331a8893a2d5775f019081b5e8ee6c0f37960x.png
2657 ms
968e0ac86b82589d9e3b453527b918022c19443f60x.gif
2646 ms
top_title_mail.gif
2644 ms
top_icon_mail.gif
2794 ms
top_btn_regist_off.jpg
2946 ms
top_title_access.gif
3088 ms
top_map.gif
3075 ms
top_title_coming.gif
3095 ms
3c5581f01a8ad1eb763e24af4e5565cfd0461e49.jpg
3879 ms
068561bddd63e3ae06907e7ae9cda8e3cff8e28f.jpg
3566 ms
8b69188779fd4f7996f3886ab5044de76d0e04c7.jpg
3654 ms
5327aefb1b4c481b7f54c3b00eac34dbf14ddf53.jpg
3575 ms
widgets.js
171 ms
804629f08c9acb57116656a9db89d6033c43a1ec.jpg
3618 ms
3fuM1d7y8FU
65 ms
www-embed-player-vflfNyN_r.css
21 ms
www-embed-player.js
42 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
29 ms
ad_status.js
39 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
29 ms
a3d66c24a46fd76e56f056dabd4c7f553891ebd1.jpg
3544 ms
e7b4c650b78603ab859baddc48e53bbd192ec479.jpg
3630 ms
7da9c60cc7c25b367c7a16f196c654ec205bab4e.jpg
3768 ms
f86582a1675a984f534bdd7fae2d91481fa62e4c.jpg
3469 ms
de57f3cbe87b881c24614a164ba9f4fd596204ba.jpg
3618 ms
68f276480abe15259e571052e567fcc88f1cb67c.jpg
3616 ms
3b36e5cc94ff86835bba2fc390205acbc6d497a0.jpg
3692 ms
9103e12c148dad7e409c56d6f40d65c4f37e4ab2.jpg
4042 ms
28438370f75b1ac25a5103c4b5cd7f25ee612f2d.jpg
3986 ms
692792b2088a26e68c6be03b731704f3a2bc7cfa.jpg
3887 ms
5a971af1a2b3bca591bbb022a32e386c33d440f6.jpg
3711 ms
aadbb4c01fc4b5ed0ad8412eae400c097ff03d26.jpg
4005 ms
19359b0abcd6a5cc795f6f7210abe44775bdbafa.jpg
3752 ms
ga.js
51 ms
11b4e83e028d04d700e2dab8c2901ee41679d4a1.jpg
3707 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
129 ms
4f9959a54bdf857ab67655ae2f25f7615a25b2b3.jpg
3538 ms
top_banner_gakuwari.jpg
4160 ms
5da598db4cc9669372db14d22172add51f1ab169.jpg
4329 ms
__utm.gif
26 ms
277d0fa08894bdf70ac75e12cb5dc79b06db141a.jpg
4333 ms
__utm.gif
2 ms
__utm.gif
5 ms
__utm.gif
3 ms
syndication
83 ms
312451904879853568
206 ms
203c.png
34 ms
1f36d.png
32 ms
1f64b.png
33 ms
2728.png
33 ms
1f606.png
33 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
39 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
145 ms
173f585f053b079a7675fe527c690571e8a74be9.jpg
4169 ms
user_icon_normal.png
195 ms
Wttdkgr7_normal.jpg
288 ms
5956932ad28f7c77e21121b69ac9bd9d_normal.jpeg
259 ms
ERfHPMOi_normal.jpg
260 ms
F3o3YxiP_normal.jpeg
342 ms
R2IZLxj7_normal.jpg
300 ms
kE_PPX3Q_normal.jpg
264 ms
0ad1MEut_normal.jpg
502 ms
uTqKrNmH_normal.jpg
372 ms
greens_logo_normal.gif
291 ms
-qMLNUIs_normal.jpg
311 ms
jaFKtyyZ_normal.jpg
422 ms
cp1vwdejuehhtkh4eazy_normal.jpeg
385 ms
pZD_SzW8_normal.jpg
340 ms
zr2DeiEq_normal.jpg
474 ms
t_-BzXqB_normal.jpg
432 ms
Cd-aRzaVIAAkgJ2.jpg:small
500 ms
Cd4-tikUYAA1QR_.jpg:small
526 ms
Cd5tdA6UAAEqGNK.jpg:small
592 ms
CdzKLgXUAAMKj1z.jpg:small
778 ms
Cd0g1GhUUAAtlaY.jpg:small
541 ms
Cd40u73VAAAjTi-.jpg:small
628 ms
Cd47ca6UsAIHrJj.jpg:small
623 ms
Cd47ca5UsAEk7r6.jpg:small
703 ms
Cd5aNoJUAAAY_0V.jpg:small
642 ms
Cd5aNoJVIAAXq4s.jpg:small
812 ms
CdwKmj8UAAESekX.jpg:small
747 ms
CdwKmspUIAAPwus.jpg:small
785 ms
CdwKnUJVAAAyH5K.jpg:small
710 ms
CdwKmoNUYAA7J7k.jpg:small
831 ms
top_banner_wedding.jpg
4141 ms
jot
28 ms
growly.net 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
growly.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
growly.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Growly.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 Growly.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.
growly.net
Open Graph description is not detected on the main page of Growly. 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: