Report Summary

  • 23

    Performance

    Renders faster than
    43% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

aurorasaurus.org

Aurorasaurus - Reporting Auroras from the Ground Up

Page Load Speed

2.5 sec in total

First Response

190 ms

Resources Loaded

2 sec

Page Rendered

256 ms

aurorasaurus.org screenshot

About Website

Click here to check amazing Aurorasaurus content for Russia. Otherwise, check out these important facts you probably never knew about aurorasaurus.org

Aurorasaurus is a citizen science site where you can report sightings of the aurora. The site contains forecasts of the Northern Lights, user-reported aurora sightings along with Tweets and photograph...

Visit aurorasaurus.org

Key Findings

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

Performance Metrics

aurorasaurus.org performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value33.1 s

0/100

25%

SI (Speed Index)

Value21.0 s

0/100

10%

TBT (Total Blocking Time)

Value21,560 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value38.3 s

0/100

10%

Network Requests Diagram

aurorasaurus.org

190 ms

aurorasaurus.org

305 ms

css

41 ms

css

65 ms

page.min.css

70 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 45% of them (29 requests) were addressed to the original Aurorasaurus.org, 15% (10 requests) were made to Maps.googleapis.com and 14% (9 requests) were made to Aurprod.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (753 ms) belongs to the original domain Aurorasaurus.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.4 kB (13%)

Content Size

1.9 MB

After Optimization

1.6 MB

In fact, the total size of Aurorasaurus.org main page is 1.9 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. 75% 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 112.5 kB

  • Original 140.3 kB
  • After minification 136.0 kB
  • After compression 27.7 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 112.5 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 55.8 kB

  • Original 1.5 MB
  • After minification 1.5 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. Aurorasaurus images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 19.6 kB

  • Original 133.7 kB
  • After minification 133.6 kB
  • After compression 114.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 19.6 kB or 15% of the original size.

CSS Optimization

-81%

Potential reduce by 52.4 kB

  • Original 64.4 kB
  • After minification 64.4 kB
  • After compression 12.0 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. Aurorasaurus.org needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (49%)

Requests Now

59

After Optimization

30

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

Accessibility Review

aurorasaurus.org accessibility score

63

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

aurorasaurus.org best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

aurorasaurus.org SEO score

81

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aurorasaurus.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Aurorasaurus.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

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