9.7 sec in total
349 ms
6.6 sec
2.7 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 349 ms and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
galileogalilei.jp performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value14.8 s
0/100
25%
Value25.5 s
0/100
10%
Value3,550 ms
1/100
30%
Value0.053
98/100
15%
Value40.1 s
0/100
10%
349 ms
1718 ms
1842 ms
34 ms
661 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 50% of them (22 requests) were addressed to the original Galileogalilei.jp, 18% (8 requests) were made to Youtube.com and 16% (7 requests) were made to Fanpla-jp.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Galileogalilei.jp.
Page size can be reduced by 2.1 MB (32%)
6.5 MB
4.4 MB
In fact, the total size of Galileogalilei.jp main page is 6.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 36.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. This page needs HTML code to be minified as it can gain 7.5 kB, which is 18% 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 36.6 kB or 85% of the original size.
Potential reduce by 1.0 MB
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. Obviously, Galileo Galilei needs image optimization as it can save up to 1.0 MB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 587.8 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 587.8 kB or 60% of the original size.
Potential reduce by 412.3 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 412.3 kB or 76% of the original size.
Number of requests can be reduced by 19 (53%)
36
17
The browser has sent 36 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 from 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
galileogalilei.jp
349 ms
www.galileogalilei.jp
1718 ms
video.min.js
1842 ms
jquery.min.js
34 ms
slick.min.js
661 ms
page--home.js
500 ms
common.js
499 ms
css2
45 ms
video-js.css
833 ms
remixicon.css
999 ms
all.min.css
1158 ms
slick.css
664 ms
slick-theme.css
826 ms
service.css
1490 ms
type01.css
991 ms
pattern_7.css
1000 ms
js
84 ms
css2
33 ms
dummy.gif
264 ms
0cabff9303e9e9aa8be5a4653335b088.png
1641 ms
iframe_api
318 ms
4a59dc5facb64f5cc514be56f946eed4.jpeg
433 ms
058836b41120778da4d84d6e8970f50e.png
753 ms
contents.png
215 ms
thumb--none.jpg
230 ms
7bdd3734f1666bf8e6b0c12475c80f30a9069486fbbfdbbab2377274777e6ebb_t.png
1574 ms
9537cfc559da0da313dcca6f83c5c98d0af7350d92ff9e68d556cde954905c10_t.png
1570 ms
9fb96a7c25aa2cd629fc5cccb31cc0ea8e0fb51f9e13670b98b079a289b1003b_t.png
1580 ms
A1020733100000031283_57585.jpeg
906 ms
A1020733100000022777_37864.jpeg
1063 ms
A1020733100000021783_35975.jpeg
1271 ms
l7gAbjR61M69yt8Z8w6FZf9WoBxdBrHbuW6O.ttf
49 ms
l7gAbjR61M69yt8Z8w6FZf9WoBxdBrGFuW6O.ttf
60 ms
l7gAbjR61M69yt8Z8w6FZf9WoBxdBrG3uW6O.ttf
60 ms
fa-solid-900.ttf
861 ms
fa-regular-400.ttf
369 ms
fa-brands-400.ttf
873 ms
www-widgetapi.js
8 ms
H6CE9uJwH8U
126 ms
y3JaJ6UIvcs
210 ms
Yvap2m65gAo
196 ms
www-player.css
7 ms
www-embed-player.js
35 ms
base.js
92 ms
galileogalilei.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
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>).
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.
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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
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
Links do not have descriptive text
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
Tap targets are not sized appropriately
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: