Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

fireworksafety.com

Pyrotechnic records and interesting facts - Firework Safety

Page Load Speed

1.6 sec in total

First Response

140 ms

Resources Loaded

1.2 sec

Page Rendered

182 ms

fireworksafety.com screenshot

About Website

Visit fireworksafety.com now to see the best up-to-date Firework Safety content for United States and also check out these interesting facts you probably never knew about fireworksafety.com

All of them were fired from four hundred places located on the coast and stretching for a hundred kilometers. Its duration was six minutes.

Visit fireworksafety.com

Key Findings

We analyzed Fireworksafety.com page load time and found that the first response time was 140 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

fireworksafety.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

fireworksafety.com

140 ms

www.fireworkssafety.org

48 ms

l9yjuhJ1HtZ7LmBAcVbMeP4C_sSsxdquJqkXzfEfnPXfeCwffFHN4UJLFRbh52jhWD9X5eB8jDIkZQsKw2FcjAmKFh93jcIaFsTaiaiaOcZTScmada4nSaFyZcmXpPozScSCZc8kZWizSclDShBcZWsoOcNkZkUl-AFGjAmCOAy8jhlljAtl5QqawKoDSWmyScmDSeBRZPoRdhXCHKol-AFGjAmCOAy8jhlljAtl5QqawKoDSWmyScmDSeBRZPoRdhXK2YgkdayTdAIldcNhjPJejAs8deU8H6qJtKGbMg62JMJ7fbKzMsMMeMb6MKG4fHXgIMMjgKMfH6qJK3IbMg6YJMJ7fbRRHyMMeMX6MKG4fHtgIMMjIfMfH6qJRMIbMg6sJMJ7fbRPFsMgeMw6MKG4fwtuIMIjgfMfH6qJXbvbMs6YJMJ7fbRQFsMgeMX6MKG4fwvuIMIj2KMfH6qJX6vbMs6sJMJ.js

54 ms

css

25 ms

118 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fireworksafety.com, 50% (15 requests) were made to Use.typekit.net and 13% (4 requests) were made to Static.squarespace.com. The less responsive or slowest element that took the longest time to load (198 ms) relates to the external source Fireworkssafety.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.7 kB (2%)

Content Size

454.9 kB

After Optimization

447.2 kB

In fact, the total size of Fireworksafety.com main page is 454.9 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. 55% of websites need less resources to load. Images take 454.7 kB which makes up the majority of the site volume.

HTML Optimization

-35%

Potential reduce by 68 B

  • Original 197 B
  • After minification 197 B
  • After compression 129 B

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 68 B or 35% of the original size.

Image Optimization

-2%

Potential reduce by 7.6 kB

  • Original 454.7 kB
  • After minification 447.1 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. Firework Safety images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 6 (46%)

Requests Now

13

After Optimization

7

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

Accessibility Review

fireworksafety.com accessibility score

94

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

fireworksafety.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fireworksafety.com SEO score

84

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fireworksafety.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 Fireworksafety.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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