Tools & Wizards About Us
patfire.com screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

patfire.com

Patriotic Fireworks - Patriotic Fireworks - Celebrating 31 Years!

Page Load Speed

1.4 sec in total

First Response

11 ms

Resources Loaded

1.3 sec

Page Rendered

90 ms

patfire.com screenshot

About Website

Click here to check amazing Patfire content. Otherwise, check out these important facts you probably never knew about patfire.com

  Patriotic Fireworks is now CLOSED. Patriotic wishes to thank all our loyal customers and many friends who have allowed us to help you celebrate JULY...

Visit patfire.com

Key Findings

We analyzed Patfire.com page load time and found that the first response time was 11 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 30% of websites can load faster.

Performance Metrics

patfire.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

patfire.com

11 ms

patfire.com

593 ms

foundation.min.css

39 ms

all.min.css

50 ms

lns7hgi.css

171 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 31% of them (8 requests) were addressed to the original Patfire.com, 23% (6 requests) were made to Cdnjs.cloudflare.com and 19% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (593 ms) belongs to the original domain Patfire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.2 kB (47%)

Content Size

308.8 kB

After Optimization

163.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 101.4 kB

  • Original 115.7 kB
  • After minification 107.9 kB
  • After compression 14.3 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 101.4 kB or 88% of the original size.

Image Optimization

-23%

Potential reduce by 42.9 kB

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

JavaScript Optimization

-7%

Potential reduce by 421 B

  • Original 6.2 kB
  • After minification 6.2 kB
  • After compression 5.8 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

-16%

Potential reduce by 507 B

  • Original 3.2 kB
  • After minification 3.2 kB
  • After compression 2.7 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. Patfire.com needs all CSS files to be minified and compressed as it can save up to 507 B or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (71%)

Requests Now

17

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

patfire.com

patfire.com

11 ms

patfire.com

patfire.com

593 ms

foundation.min.css

foundation.min.css

39 ms

all.min.css

all.min.css

50 ms

lns7hgi.css

lns7hgi.css

171 ms

slick.css

slick.css

28 ms

stylesheet_combined_20ca5e11ae13453df4886ee557a19ddc.css

stylesheet_combined_20ca5e11ae13453df4886ee557a19ddc.css

61 ms

lbformnew.js

lbformnew.js

424 ms

header_logo_1200.png

header_logo_1200.png

345 ms

afw_logo_transparent.png

afw_logo_transparent.png

291 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

32 ms

foundation.min.js

foundation.min.js

53 ms

cart.js

cart.js

264 ms

slick.min.js

slick.min.js

28 ms

cgejs_b97ff89502af44ba3be2e82ae1c50f435845809a.js

cgejs_b97ff89502af44ba3be2e82ae1c50f435845809a.js

263 ms

p.css

p.css

15 ms

tracker.bundle.js

tracker.bundle.js

202 ms

fa-solid-900.woff

fa-solid-900.woff

17 ms

fa-regular-400.woff

fa-regular-400.woff

10 ms

d

d

11 ms

d

d

21 ms

d

d

27 ms

d

d

30 ms

stylesheet_combined_1237dcbf838683040afaf4df39a8cf9d.css

stylesheet_combined_1237dcbf838683040afaf4df39a8cf9d.css

60 ms

image8311910.png

image8311910.png

203 ms

fa-brands-400.woff

fa-brands-400.woff

15 ms

Accessibility Review

patfire.com accessibility score

87

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

[role]s are not contained by their required parent element

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

Best Practices

patfire.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

High

Page has valid source maps

SEO Factors

patfire.com SEO score

89

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patfire.com 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 Patfire.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

patfire.com

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