Tools & Wizards About Us
flareaware.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

flareaware.com

Solar Flare Alerts | About Solar Flares | Warnings | Solar Flare Storms - FlareAware.com

Page Load Speed

1.9 sec in total

First Response

51 ms

Resources Loaded

1.5 sec

Page Rendered

307 ms

flareaware.com screenshot

About Website

Click here to check amazing Flare Aware content. Otherwise, check out these important facts you probably never knew about flareaware.com

What is a solar storm? Do you know? If this Storm hits earth it will take Millions of People's lives, Get solar flare alerts and other weather alerts at FlareAware.com

Visit flareaware.com

Key Findings

We analyzed Flareaware.com page load time and found that the first response time was 51 ms and then it took 1.8 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

flareaware.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

flareaware.com

51 ms

flareaware.com

91 ms

application-9c4c7cb20bfeacfb58e382b0bb7817e9f82b45e66112d81a153016049f0b432c.css

140 ms

element.js

53 ms

application-2965af03a69208977ae24dc12c3ca8f9c2f521acc7823e535157d9e2bf445f61.js

282 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 37% of them (29 requests) were addressed to the original Flareaware.com, 26% (20 requests) were made to Platform.twitter.com and 8% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (814 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.9 kB (5%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flareaware.com main page is 1.2 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. Javascripts take 784.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 44.6 kB

  • Original 61.3 kB
  • After minification 61.2 kB
  • After compression 16.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 44.6 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 12.6 kB

  • Original 266.4 kB
  • After minification 253.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. Flare Aware images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.7 kB

  • Original 784.7 kB
  • After minification 784.7 kB
  • After compression 783.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 51.8 kB
  • After minification 51.8 kB
  • After compression 51.8 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. Flareaware.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

68

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flareaware.com

flareaware.com

51 ms

flareaware.com

flareaware.com

91 ms

application-9c4c7cb20bfeacfb58e382b0bb7817e9f82b45e66112d81a153016049f0b432c.css

application-9c4c7cb20bfeacfb58e382b0bb7817e9f82b45e66112d81a153016049f0b432c.css

140 ms

element.js

element.js

53 ms

application-2965af03a69208977ae24dc12c3ca8f9c2f521acc7823e535157d9e2bf445f61.js

application-2965af03a69208977ae24dc12c3ca8f9c2f521acc7823e535157d9e2bf445f61.js

282 ms

all.js

all.js

29 ms

claim.js

claim.js

84 ms

E-v1.js

E-v1.js

36 ms

widgets.js

widgets.js

19 ms

PinExt.png

PinExt.png

27 ms

woahbar-up-arrow.png

woahbar-up-arrow.png

178 ms

background-nebula.jpg

background-nebula.jpg

108 ms

logo-c66d87f8016395981d80f5ddb466b3e41b9faf30aade4b944a187897bef96cde.png

logo-c66d87f8016395981d80f5ddb466b3e41b9faf30aade4b944a187897bef96cde.png

107 ms

blank-coming-soon-4d2c573474860f57e418e1a896644fb11cc10e60f0a521bcd16486d4f2633436.png

blank-coming-soon-4d2c573474860f57e418e1a896644fb11cc10e60f0a521bcd16486d4f2633436.png

106 ms

glyphicons-halflings-80dfe6854eab05fef99752d65528b45078554ce65a627dd140d535da5509cbc8.png

glyphicons-halflings-80dfe6854eab05fef99752d65528b45078554ce65a627dd140d535da5509cbc8.png

105 ms

check.png

check.png

118 ms

testi-face-george-dc6951cf6300a6f1647b66748f810c126a6a0a5e7690cb1b8b96655ec374a33b.jpg

testi-face-george-dc6951cf6300a6f1647b66748f810c126a6a0a5e7690cb1b8b96655ec374a33b.jpg

175 ms

testi-face-kati-b9e55a2984293060b2910e561a9eb23bbb004535e6536808786ed3a58f9e8191.jpg

testi-face-kati-b9e55a2984293060b2910e561a9eb23bbb004535e6536808786ed3a58f9e8191.jpg

176 ms

testi-face-ted-e7a322a89f04ec362f280e2d20711ec55093af0050bedafe89fc23dd92c65819.jpg

testi-face-ted-e7a322a89f04ec362f280e2d20711ec55093af0050bedafe89fc23dd92c65819.jpg

177 ms

testi-face-sally-fca110eab50fd71a32a05bfcb5f87a6e924448f51f0a17e7191ce417bd2b72df.jpg

testi-face-sally-fca110eab50fd71a32a05bfcb5f87a6e924448f51f0a17e7191ce417bd2b72df.jpg

240 ms

testi-face-peter-7bcc500784619822d29593607ff0c555a543a9474408818993be11db948c499f.jpg

testi-face-peter-7bcc500784619822d29593607ff0c555a543a9474408818993be11db948c499f.jpg

240 ms

testi-face-bryant-da0ef42ca314d55d7272c7d0ce0828592313651d33c07dbe3bc5619d39bc2615.jpg

testi-face-bryant-da0ef42ca314d55d7272c7d0ce0828592313651d33c07dbe3bc5619d39bc2615.jpg

241 ms

family-1a25e5f4bdfa03fd9cd516ef3d6588d1acd120dd1d09c9f5c7c456ba17391af6.png

family-1a25e5f4bdfa03fd9cd516ef3d6588d1acd120dd1d09c9f5c7c456ba17391af6.png

240 ms

heart-2e82863937755da0ba063538a6c23ed3d3ea4f2db201f140c37703bd1575828f.png

heart-2e82863937755da0ba063538a6c23ed3d3ea4f2db201f140c37703bd1575828f.png

239 ms

paypal_verification_seal-dc2a309ef0a9821c5bb508a4469739398f626ff7f3cb585440ef3aaa0311c335.png

paypal_verification_seal-dc2a309ef0a9821c5bb508a4469739398f626ff7f3cb585440ef3aaa0311c335.png

239 ms

twitter-cabccb50e7e784fd145a4c0eb42d021caf0dd4b8bd4d984ac8bddef14e3897cb.png

twitter-cabccb50e7e784fd145a4c0eb42d021caf0dd4b8bd4d984ac8bddef14e3897cb.png

307 ms

facebook-bf406a4149113350cf8a04db136789e03355b0cde2977a6af7e7e8789673bf16.png

facebook-bf406a4149113350cf8a04db136789e03355b0cde2977a6af7e7e8789673bf16.png

297 ms

youtube-747e045a776e7e1be27f504bc44f38acde9f3b7acb3799f825b2a91364ecbcc3.png

youtube-747e045a776e7e1be27f504bc44f38acde9f3b7acb3799f825b2a91364ecbcc3.png

307 ms

linkedin-6895861b49253de6bb13ae01eb229290e82b9c346958f88fd6e7713f60268317.png

linkedin-6895861b49253de6bb13ae01eb229290e82b9c346958f88fd6e7713f60268317.png

352 ms

woahbar-down-arrow.png

woahbar-down-arrow.png

102 ms

yanone_kaffeesatz_regular-webfont.woff

yanone_kaffeesatz_regular-webfont.woff

182 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

182 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

225 ms

OpenSans-ExtraBold-webfont.woff

OpenSans-ExtraBold-webfont.woff

228 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

238 ms

all.js

all.js

57 ms

plusone.js

plusone.js

138 ms

ga.js

ga.js

123 ms

mlt.js

mlt.js

422 ms

main.js

main.js

300 ms

woopra.js

woopra.js

155 ms

f5d4ed2c29.json

f5d4ed2c29.json

182 ms

8efe3998fe.json

8efe3998fe.json

276 ms

56fbad7984.json

56fbad7984.json

246 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

63 ms

130 ms

__utm.gif

__utm.gif

43 ms

settings

settings

228 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

26 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

41 ms

fastbutton

fastbutton

38 ms

postmessageRelay

postmessageRelay

33 ms

2254111616-postmessagerelay.js

2254111616-postmessagerelay.js

26 ms

rpc:shindig_random.js

rpc:shindig_random.js

11 ms

flashPlayer.js

flashPlayer.js

32 ms

wistiaLogo.js

wistiaLogo.js

41 ms

developers.google.com

developers.google.com

814 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

5 ms

embeds

embeds

114 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

12 ms

FlareAware

FlareAware

291 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

3 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

19 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

24 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

22 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

22 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

48 ms

_buildManifest.js

_buildManifest.js

59 ms

_ssgManifest.js

_ssgManifest.js

58 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

12 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

3 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

27 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

27 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

7 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

5 ms

Accessibility Review

flareaware.com accessibility score

80

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

Heading elements are not in a sequentially-descending order

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

Best Practices

flareaware.com best practices score

58

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

flareaware.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Flareaware.com 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 Flareaware.com 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

flareaware.com

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