1.9 sec in total
211 ms
1.4 sec
342 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
Visit gotfireworks.comWe analyzed Gotfireworks.com page load time and found that the first response time was 211 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
gotfireworks.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value14.4 s
0/100
25%
Value5.3 s
58/100
10%
Value160 ms
93/100
30%
Value0.473
18/100
15%
Value14.6 s
8/100
10%
211 ms
43 ms
97 ms
72 ms
73 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 95% of them (168 requests) were addressed to the original Gotfireworks.com, 4% (7 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (272 ms) belongs to the original domain Gotfireworks.com.
Page size can be reduced by 234.8 kB (12%)
2.0 MB
1.7 MB
In fact, the total size of Gotfireworks.com main page is 2.0 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 105.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 105.6 kB or 86% of the original size.
Potential reduce by 3.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 118.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 118.1 kB or 27% of the original size.
Potential reduce by 7.1 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 135 (84%)
161
26
The browser has sent 161 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 109 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
gotfireworks.com
211 ms
calendar.css
43 ms
styles-m.css
97 ms
styles.css
72 ms
owl.carousel.min.css
73 ms
animate.css
76 ms
fontawesome5.css
78 ms
mgz_font.css
75 ms
mgz_bootstrap.css
109 ms
openiconic.min.css
95 ms
styles.css
112 ms
common.css
111 ms
magnific.css
110 ms
ionslider.css
118 ms
intlTelInput.min.css
119 ms
styles.css
122 ms
photoswipe.css
124 ms
default-skin.css
125 ms
blueimp-gallery.min.css
126 ms
styles.css
141 ms
styles.css
143 ms
styles.css
145 ms
widget.css
146 ms
attributepages.css
147 ms
crosslinks.css
149 ms
styles-l.css
174 ms
css-fix.css
167 ms
require.js
177 ms
mixins.js
170 ms
requirejs-config.js
177 ms
css2
30 ms
print.css
175 ms
avada-popup.min.js
125 ms
Got-Fireworks-Site-logo-75.png
152 ms
back-yard-bbq-sm.jpg
152 ms
200-gram-cakes.jpg
153 ms
ball-shell-sm.jpg
152 ms
60--gram-sm.jpg
153 ms
500-gram-zipper.jpg
153 ms
racks-sm.jpg
181 ms
firecracker-sm.jpg
182 ms
roman-cnadle-sm.jpg
182 ms
witch-doctor-%7C-42-shot-500-gram-multi-shot-aerial-firework-by-no-name-fireworks.jpg
181 ms
fake-news-alert-%7C-25-shot-500-gram-multi-shot-aerial-by-no-name-fireworks.jpg
182 ms
thunder-and-lightning-%7C-5-inch-24-shot-60-gram-reloadable-canister-shell-by-no-name-fireworks.jpg
182 ms
gorilla-warfare-%7C-25-shot-500-gram-multi-shot-aerial-by-no-name-fireworks.jpg
197 ms
icon_quality.png
196 ms
icon_cost.png
196 ms
icon_customer-services.png
197 ms
logo.png
207 ms
jquery.js
233 ms
common.js
217 ms
dataPost.js
217 ms
bootstrap.js
220 ms
app.js
220 ms
form-key-provider.js
227 ms
mage-translation-dictionary.js
245 ms
theme.js
244 ms
opensans-400.woff
255 ms
opensans-300.woff
255 ms
opensans-600.woff
272 ms
opensans-700.woff
271 ms
KFOmCnqEu92Fr1Me5g.woff
18 ms
KFOlCnqEu92Fr1MmEU9vAA.woff
37 ms
KFOlCnqEu92Fr1MmSU5vAA.woff
48 ms
KFOkCnqEu92Fr1MmgWxM.woff
47 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
48 ms
KFOlCnqEu92Fr1MmYUtvAA.woff
47 ms
fa-solid-900.woff
220 ms
fa-regular-400.woff
172 ms
Blank-Theme-Icons.woff
184 ms
Yq6R-LCAWCX3-6Ky7FAFnOU.woff
48 ms
mgz_openiconic.woff
184 ms
jquery.waypoints.js
182 ms
domReady.js
104 ms
template.js
103 ms
confirm.js
103 ms
widget.js
104 ms
main.js
102 ms
bootstrap.js
103 ms
jquery-mixin.js
101 ms
types.js
113 ms
layout.js
112 ms
jquery-migrate.js
109 ms
slider.js
94 ms
common.js
94 ms
text.js
99 ms
smart-keyboard-handler.js
98 ms
mage.js
99 ms
ie-class-fixer.js
103 ms
underscore.js
31 ms
translate.js
29 ms
modal.js
34 ms
knockout.js
62 ms
knockout-es5.js
39 ms
wrapper.js
46 ms
scripts.js
36 ms
version.js
38 ms
main.js
39 ms
registry.js
53 ms
player.js
54 ms
engine.js
56 ms
bootstrap.js
58 ms
observable_array.js
62 ms
bound-nodes.js
67 ms
js-translation.json
67 ms
console-logger.js
73 ms
owl.carousel.min.js
80 ms
modal-popup.html
69 ms
modal-slide.html
107 ms
modal-custom.html
107 ms
key-codes.js
108 ms
core.js
108 ms
z-index.js
109 ms
arrays.js
84 ms
compare.js
84 ms
misc.js
84 ms
objects.js
85 ms
strings.js
90 ms
template.js
91 ms
knockout-repeat.js
72 ms
knockout-fast-foreach.js
74 ms
observable_source.js
78 ms
renderer.js
78 ms
resizable.js
85 ms
i18n.js
90 ms
scope.js
91 ms
range.js
94 ms
mage-init.js
100 ms
keyboard.js
100 ms
optgroup.js
107 ms
after-render.js
113 ms
autoselect.js
114 ms
datepicker.js
116 ms
outer_click.js
122 ms
fadeVisible.js
123 ms
collapsible.js
130 ms
staticChecked.js
135 ms
simple-checked.js
136 ms
bind-html.js
138 ms
tooltip.js
143 ms
color-picker.js
143 ms
events.js
143 ms
local.js
142 ms
logger.js
106 ms
entry-factory.js
107 ms
console-output-handler.js
113 ms
formatter.js
114 ms
message-pool.js
119 ms
levels-pool.js
125 ms
logger-utils.js
126 ms
gotfireworks.com
206 ms
slider2.png
220 ms
data.js
125 ms
disable-selection.js
132 ms
focusable.js
137 ms
form.js
138 ms
ie.js
148 ms
keycode.js
152 ms
labels.js
155 ms
jquery-patch.js
150 ms
plugin.js
153 ms
safe-active-element.js
160 ms
safe-blur.js
162 ms
scroll-parent.js
158 ms
tabbable.js
168 ms
unique-id.js
168 ms
class.js
166 ms
loader.js
168 ms
async.js
173 ms
tooltip.html
143 ms
spectrum.js
158 ms
tinycolor.js
157 ms
entry.js
136 ms
moment.js
139 ms
dom-observer.js
25 ms
bindings.js
27 ms
gotfireworks.com accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
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: