Tools & Wizards About Us
gaiaverse.eu screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gaiaverse.eu

Gaiaverse | Brought to you by the European Cooperation in Science and Technology

Page Load Speed

4 sec in total

First Response

310 ms

Resources Loaded

3.6 sec

Page Rendered

160 ms

gaiaverse.eu screenshot

About Website

Click here to check amazing Gaiaverse content. Otherwise, check out these important facts you probably never knew about gaiaverse.eu

Genius is an european project to provide an easy acces to the outstanding astronomical data of the Gaia mission

Visit gaiaverse.eu

Key Findings

We analyzed Gaiaverse.eu page load time and found that the first response time was 310 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

gaiaverse.eu performance score

0

Network Requests Diagram

310 ms

wp-emoji-release.min.js

95 ms

style.min.css

191 ms

resources-styles.css

290 ms

genericons.css

380 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 54% of them (38 requests) were addressed to the original Gaiaverse.eu, 26% (18 requests) were made to Platform.twitter.com and 10% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (959 ms) belongs to the original domain Gaiaverse.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.3 kB (16%)

Content Size

1.1 MB

After Optimization

909.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gaiaverse.eu main page is 1.1 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. 65% of websites need less resources to load. Images take 880.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 19.7 kB

  • Original 27.2 kB
  • After minification 25.7 kB
  • After compression 7.4 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 19.7 kB or 73% of the original size.

Image Optimization

-15%

Potential reduce by 128.1 kB

  • Original 880.2 kB
  • After minification 752.0 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. Obviously, Gaiaverse needs image optimization as it can save up to 128.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 14.1 kB

  • Original 115.3 kB
  • After minification 115.3 kB
  • After compression 101.2 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 14.1 kB or 12% of the original size.

CSS Optimization

-11%

Potential reduce by 6.3 kB

  • Original 55.5 kB
  • After minification 55.5 kB
  • After compression 49.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. Gaiaverse.eu needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (65%)

Requests Now

62

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gaiaverse. 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.

Network Requests Diagram

310 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

95 ms

style.min.css

style.min.css

191 ms

resources-styles.css

resources-styles.css

290 ms

genericons.css

genericons.css

380 ms

style.css

style.css

392 ms

front.min.css

front.min.css

294 ms

jquery.min.js

jquery.min.js

499 ms

jquery-migrate.min.js

jquery-migrate.min.js

295 ms

jquery.mCustomScrollbar.js

jquery.mCustomScrollbar.js

473 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

385 ms

jquery.fancybox.js

jquery.fancybox.js

390 ms

generic_script.js

generic_script.js

470 ms

front.min.js

front.min.js

477 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

482 ms

jquery.fancybox.css

jquery.fancybox.css

536 ms

widgets.js

widgets.js

18 ms

comment-reply.min.js

comment-reply.min.js

583 ms

imagesloaded.min.js

imagesloaded.min.js

582 ms

masonry.min.js

masonry.min.js

582 ms

jquery.masonry.min.js

jquery.masonry.min.js

581 ms

functions.js

functions.js

603 ms

wp-embed.min.js

wp-embed.min.js

611 ms

css

css

19 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

64 ms

res_image.png

res_image.png

158 ms

catalog_icon.png

catalog_icon.png

147 ms

app_icon.png

app_icon.png

146 ms

Gaia-image-milky-way.png

Gaia-image-milky-way.png

517 ms

logos.png

logos.png

158 ms

analytics.js

analytics.js

46 ms

lupa.png

lupa.png

158 ms

search_arrow.png

search_arrow.png

220 ms

separador.gif

separador.gif

221 ms

share_link.png

share_link.png

231 ms

facebook_white.png

facebook_white.png

231 ms

twitter_white.png

twitter_white.png

248 ms

gplus_white.png

gplus_white.png

310 ms

mail_white.png

mail_white.png

318 ms

Gaia-BH3-baner.png

Gaia-BH3-baner.png

429 ms

MWGaia-Legacy-Map-Baner.png

MWGaia-Legacy-Map-Baner.png

601 ms

Gaia-DR3.png

Gaia-DR3.png

959 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

9 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

27 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

27 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

28 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

28 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

28 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

27 ms

collect

collect

37 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

39 ms

js

js

64 ms

settings

settings

73 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

4 ms

ESAGaia

ESAGaia

583 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

4 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

16 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

22 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

20 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

20 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

20 ms

_buildManifest.js

_buildManifest.js

21 ms

_ssgManifest.js

_ssgManifest.js

21 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

8 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

9 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

3 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

7 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

14 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

14 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

13 ms

SEO Factors

gaiaverse.eu SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gaiaverse.eu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Gaiaverse.eu 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.

Social Sharing Optimization

gaiaverse.eu

Open Graph description is not detected on the main page of Gaiaverse. 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: