Tools & Wizards About Us
helioviewer.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

helioviewer.org

Helioviewer.org - Solar and heliospheric image visualization tool

Page Load Speed

677 ms in total

First Response

58 ms

Resources Loaded

459 ms

Page Rendered

160 ms

helioviewer.org screenshot

About Website

Click here to check amazing Helioviewer content for Brazil. Otherwise, check out these important facts you probably never knew about helioviewer.org

Helioviewer.org - Solar and heliospheric image visualization tool

Visit helioviewer.org

Key Findings

We analyzed Helioviewer.org page load time and found that the first response time was 58 ms and then it took 619 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

helioviewer.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value3,370 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

helioviewer.org

58 ms

reset-fonts.css

17 ms

jquery-ui-1.8.12.custom.css

19 ms

jquery.jgrowl.css

16 ms

jquery.qtip.min.css

17 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 94% of them (60 requests) were addressed to the original Helioviewer.org, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (150 ms) relates to the external source Ajax.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 407.9 kB (57%)

Content Size

712.0 kB

After Optimization

304.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Helioviewer.org main page is 712.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 378.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 39.6 kB

  • Original 48.6 kB
  • After minification 38.0 kB
  • After compression 9.0 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 10.6 kB, which is 22% 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 39.6 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 40.2 kB

  • Original 207.9 kB
  • After minification 167.8 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, Helioviewer needs image optimization as it can save up to 40.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 265.3 kB

  • Original 378.6 kB
  • After minification 374.5 kB
  • After compression 113.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 265.3 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 62.8 kB

  • Original 76.9 kB
  • After minification 65.2 kB
  • After compression 14.1 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. Helioviewer.org needs all CSS files to be minified and compressed as it can save up to 62.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (54%)

Requests Now

63

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Helioviewer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

helioviewer.org

helioviewer.org

58 ms

reset-fonts.css

reset-fonts.css

17 ms

jquery-ui-1.8.12.custom.css

jquery-ui-1.8.12.custom.css

19 ms

jquery.jgrowl.css

jquery.jgrowl.css

16 ms

jquery.qtip.min.css

jquery.qtip.min.css

17 ms

imgareaselect-default.css

imgareaselect-default.css

18 ms

dot-luv.css

dot-luv.css

18 ms

helioviewer.min.css

helioviewer.min.css

20 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

13 ms

jquery-ui.min.js

jquery-ui.min.js

150 ms

jquery.class.min.js

jquery.class.min.js

16 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

11 ms

date-en-US.js

date-en-US.js

36 ms

jquery.qtip.min.js

jquery.qtip.min.js

38 ms

jquery.number.min.js

jquery.number.min.js

34 ms

jquery.json-2.3.min.js

jquery.json-2.3.min.js

35 ms

jquery.cookie.min.js

jquery.cookie.min.js

34 ms

jquery.cookiejar.pack.js

jquery.cookiejar.pack.js

35 ms

jquery.jgrowl_minimized.js

jquery.jgrowl_minimized.js

37 ms

jquery.imgareaselect.pack.js

jquery.imgareaselect.pack.js

36 ms

jquery.jfeed.js

jquery.jfeed.js

36 ms

jquery.xml2json.pack.js

jquery.xml2json.pack.js

36 ms

jquery.jstree.min.js

jquery.jstree.min.js

35 ms

helioviewer.min.js

helioviewer.min.js

81 ms

ga.js

ga.js

39 ms

gradient_v5-optimized.png

gradient_v5-optimized.png

15 ms

ui-bg_gloss-wave_20_111111_500x100.png

ui-bg_gloss-wave_20_111111_500x100.png

10 ms

glass_button_square_24px_white.png

glass_button_square_24px_white.png

10 ms

glass_slider_trough_vertical_white.png

glass_slider_trough_vertical_white.png

9 ms

transparentBGWhite.png

transparentBGWhite.png

8 ms

ui-icons_e8e8e8_256x240.png

ui-icons_e8e8e8_256x240.png

12 ms

simple.png

simple.png

13 ms

youtube_79x32.png

youtube_79x32.png

13 ms

ajax-loader-videos.gif

ajax-loader-videos.gif

13 ms

ui-bg_gloss-wave_20_111111_500x100_transparent_15.png

ui-bg_gloss-wave_20_111111_500x100_transparent_15.png

15 ms

ajax-loader.gif

ajax-loader.gif

16 ms

transparentBG50.png

transparentBG50.png

16 ms

youtube.png

youtube.png

17 ms

__utm.gif

__utm.gif

15 ms

calendar_small.png

calendar_small.png

38 ms

index.php

index.php

38 ms

index.php

index.php

30 ms

index.php

index.php

35 ms

index.php

index.php

136 ms

ui-bg_dots-small_20_333333_2x2.png

ui-bg_dots-small_20_333333_2x2.png

29 ms

LayerManagerButton_Visibility_Visible.png

LayerManagerButton_Visibility_Visible.png

30 ms

labels_visible_10x10.png

labels_visible_10x10.png

30 ms

glass_slider_handle_white.png

glass_slider_handle_white.png

31 ms

earth.png

earth.png

30 ms

index.php

index.php

21 ms

index.php

index.php

80 ms

index.php

index.php

99 ms

glass_slider_trough_horiztonal_white.png

glass_slider_trough_horiztonal_white.png

68 ms

style.css

style.css

89 ms

index.php

index.php

39 ms

index.php

index.php

15 ms

index.php

index.php

18 ms

index.php

index.php

18 ms

index.php

index.php

23 ms

preview-small.png

preview-small.png

16 ms

preview-small.png

preview-small.png

9 ms

preview-small.png

preview-small.png

17 ms

d.png

d.png

9 ms

AR@2x.png

AR@2x.png

11 ms

Accessibility Review

helioviewer.org accessibility score

78

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

helioviewer.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

helioviewer.org SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Helioviewer.org 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 Helioviewer.org 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

helioviewer.org

Open Graph data is detected on the main page of Helioviewer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: