13.2 sec in total
649 ms
8.5 sec
4 sec
Click here to check amazing Galileo Galilei content for Japan. Otherwise, check out these important facts you probably never knew about galileogalilei.jp
GG Friends - Galileo Galileiオフィシャルファンクラブ
Visit galileogalilei.jpWe analyzed Galileogalilei.jp page load time and found that the first response time was 649 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
galileogalilei.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value20.6 s
0/100
25%
Value6.3 s
42/100
10%
Value1,030 ms
26/100
30%
Value0.093
91/100
15%
Value7.4 s
48/100
10%
649 ms
781 ms
24 ms
572 ms
988 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 90% of them (46 requests) were addressed to the original Galileogalilei.jp, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Sonymusic.co.jp. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Galileogalilei.jp.
Page size can be reduced by 97.9 kB (3%)
3.0 MB
2.9 MB
In fact, the total size of Galileogalilei.jp main page is 3.0 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. 15% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 7.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. This page needs HTML code to be minified as it can gain 1.2 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 7.1 kB or 74% of the original size.
Potential reduce by 50.4 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. Galileo Galilei images are well optimized though.
Potential reduce by 27.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 27.1 kB or 43% of the original size.
Potential reduce by 13.2 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. Galileogalilei.jp needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 83% of the original size.
Number of requests can be reduced by 11 (29%)
38
27
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Galileo Galilei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
galileogalilei.jp
649 ms
www.galileogalilei.jp
781 ms
css
24 ms
style.css
572 ms
s_code.js
988 ms
conversion.js
22 ms
01_home.png
199 ms
gg-bg.jpg
5722 ms
header-bg.jpg
1162 ms
logo2.png
576 ms
m-media.png
386 ms
m-blog.png
397 ms
ega-001.png
3841 ms
cd-4th-album.png
1522 ms
cd-new.png
1382 ms
ega-004.jpg
1529 ms
tote-005.png
4446 ms
rec-006.png
2958 ms
pic-012.png
2091 ms
pic-011.png
1911 ms
pic-010.png
2486 ms
pic-007.png
2472 ms
pic-008.png
3042 ms
pic-009.png
3060 ms
t-016.png
6692 ms
ega-013.png
3416 ms
ega-014.png
3243 ms
ega-015.png
3816 ms
02_news.png
374 ms
04_disco.png
382 ms
03_bio.png
390 ms
05_live.png
388 ms
06_shop.png
417 ms
twitter_a.png
385 ms
fb_a.png
558 ms
yt_a.png
560 ms
m_a.png
607 ms
g_a.png
610 ms
01_home.png
3428 ms
02_news.png
3424 ms
04_disco.png
3607 ms
05_live.png
3622 ms
03_bio.png
3639 ms
twitter_a.png
3783 ms
06_shop.png
3779 ms
fb_a.png
3663 ms
yt_a.png
3800 ms
m_a.png
3775 ms
g_a.png
3816 ms
s84046833792235
37 ms
42 ms
galileogalilei.jp accessibility score
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
Image elements do not have [alt] attributes
galileogalilei.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
galileogalilei.jp 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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Galileogalilei.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Galileogalilei.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.
galileogalilei.jp
Open Graph description is not detected on the main page of Galileo Galilei. 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: