4 sec in total
657 ms
2.8 sec
579 ms
Welcome to gotfireworks.com homepage info - get ready to check Got Fireworks best content for United States right away, or after learning these important things about gotfireworks.com
Buy wholesale fireworks online at great prices, wide assortment of ground and aerial fireworks on sale now!
Visit gotfireworks.comWe analyzed Gotfireworks.com page load time and found that the first response time was 657 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
gotfireworks.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value6.9 s
6/100
25%
Value18.4 s
0/100
10%
Value59,330 ms
0/100
30%
Value0.023
100/100
15%
Value78.2 s
0/100
10%
657 ms
105 ms
126 ms
170 ms
202 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gotfireworks.com, 96% (78 requests) were made to Static.gotfireworks.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.gotfireworks.com.
Page size can be reduced by 301.5 kB (17%)
1.8 MB
1.5 MB
In fact, the total size of Gotfireworks.com main page is 1.8 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. 80% 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.1 MB which makes up the majority of the site volume.
Potential reduce by 82.6 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 82.6 kB or 83% of the original size.
Potential reduce by 45.9 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. Got Fireworks images are well optimized though.
Potential reduce by 163.0 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 163.0 kB or 44% of the original size.
Potential reduce by 10.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. Gotfireworks.com has all CSS files already compressed.
Number of requests can be reduced by 60 (77%)
78
18
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Got Fireworks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
gotfireworks.com
657 ms
css
105 ms
styles-m.css
126 ms
angular-material.css
170 ms
default.css
202 ms
form-builder.css
212 ms
form-render.css
209 ms
google-map.css
209 ms
jquery.fancyambox.min.css
236 ms
amhideprice.css
238 ms
balance.css
241 ms
gallery.css
255 ms
cart.css
240 ms
rule-popup.css
237 ms
promo-block-widget.css
240 ms
category-badges.css
254 ms
pointofsale.css
267 ms
preferred-store.css
276 ms
styles-l.css
267 ms
fontawesome-all.css
244 ms
owl.carousel.min.css
236 ms
header-styles.css
297 ms
footer-styles.css
249 ms
main-styles.css
267 ms
gotfireworks-logo.png
236 ms
gotfireworks-logo.png
281 ms
require.js
217 ms
mixins.js
218 ms
requirejs-config.js
219 ms
polyfill.js
220 ms
2021-shell-banner.jpg
408 ms
2021-nonname-mgea-5-line-mobile.jpg
446 ms
nn5041-500-gram-cake.png
406 ms
nn4006-artillery-shells.png
399 ms
nn2020-200gram-cake-shadow.png
406 ms
nn0445-bottle-rocket.png
403 ms
NN6004-web.jpg
405 ms
nn5066-Combined-web.jpg
406 ms
got-shop-pro-2-23.jpg
1361 ms
got-free-shipping-748-748.jpg
297 ms
wholeslae-account-image.jpg
1345 ms
no-name-pay-powder-748.jpg
305 ms
footer-payment.png
265 ms
cfed010a134e3960da2ec751898d9687.png
294 ms
fontawesome-webfont.woff
102 ms
CodazonFont.ttf
59 ms
jquery.mobile.custom.js
38 ms
ajax-post.js
38 ms
bootstrap.js
38 ms
jquery.js
39 ms
translate-inline.js
37 ms
responsive.js
36 ms
theme.js
37 ms
themecore.js
37 ms
translate.js
84 ms
domReady.js
84 ms
modal.js
84 ms
mage.js
86 ms
jquery.cookie.js
58 ms
template.js
57 ms
confirm.js
59 ms
dataPost.js
59 ms
main.js
57 ms
bootstrap.js
58 ms
api.js
866 ms
common.js
32 ms
jquery-migrate.js
32 ms
tabs.js
31 ms
smart-keyboard-handler.js
31 ms
ie-class-fixer.js
30 ms
jquery.js
48 ms
jquery-ui.js
48 ms
angular-material-bundle.js
28 ms
matchMedia.js
29 ms
underscore.js
26 ms
text.js
26 ms
key-codes.js
26 ms
knockout.js
25 ms
knockout-es5.js
24 ms
collapsible.js
85 ms
jquery-ui.js
70 ms
gotfireworks.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gotfireworks.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
gotfireworks.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gotfireworks.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 Gotfireworks.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.
gotfireworks.com
Open Graph description is not detected on the main page of Got Fireworks. 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: