3 sec in total
245 ms
2.2 sec
506 ms
Click here to check amazing Moto Horn content for United States. Otherwise, check out these important facts you probably never knew about motohorn.com
Loud motorcycle horn upgrades with proven quality & money-back loudness guarantee. Backed by 100,000+ riders in the United States. Genuine US registered trademark.
Visit motohorn.comWe analyzed Motohorn.com page load time and found that the first response time was 245 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
motohorn.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value3.9 s
51/100
25%
Value4.0 s
81/100
10%
Value500 ms
58/100
30%
Value0.154
75/100
15%
Value7.1 s
52/100
10%
245 ms
82 ms
42 ms
60 ms
54 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 95% of them (97 requests) were addressed to the original Motohorn.com, 3% (3 requests) were made to Stats.wp.com and 2% (2 requests) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Motohorn.com.
Page size can be reduced by 373.7 kB (11%)
3.4 MB
3.0 MB
In fact, the total size of Motohorn.com main page is 3.4 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 2.9 MB which makes up the majority of the site volume.
Potential reduce by 373.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 373.6 kB or 87% of the original size.
Potential reduce by 0 B
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. Moto Horn images are well optimized though.
Potential reduce by 66 B
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.
Number of requests can be reduced by 44 (49%)
90
46
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moto Horn. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
motohorn.com
245 ms
motohorn.com
82 ms
dashicons.min.css
42 ms
thickbox.css
60 ms
metorik.css
54 ms
flags-64.min.css
134 ms
eh-paypal-style.css
176 ms
flatsome.css
66 ms
flatsome-shop.css
81 ms
style.css
82 ms
jquery.min.js
91 ms
jquery-migrate.min.js
98 ms
wp-polyfill-inert.min.js
151 ms
regenerator-runtime.min.js
112 ms
wp-polyfill.min.js
132 ms
hooks.min.js
134 ms
w.js
36 ms
jquery.blockUI.min.js
143 ms
add-to-cart.min.js
161 ms
js.cookie.min.js
169 ms
default-display-images.min.js
1105 ms
script.min.js
170 ms
shortcode-script.min.js
1105 ms
s-202410.js
37 ms
jquery.bind-first-0.2.3.min.js
1106 ms
js.cookie-2.1.3.min.js
1112 ms
public.js
1105 ms
wpforms-full.min.css
1109 ms
thickbox.js
1101 ms
woocommerce.min.js
1107 ms
sourcebuster.min.js
1105 ms
order-attribution.min.js
1117 ms
metorik.min.js
1109 ms
hoverIntent.min.js
1110 ms
flatsome.js
1112 ms
flatsome-wp-rocket.js
1113 ms
flatsome-live-search.js
1115 ms
woocommerce.js
1117 ms
e-202410.js
27 ms
utm-tracker.min.js
1116 ms
cart-fragments.min.js
1117 ms
jquery.validate.min.js
1093 ms
mailcheck.min.js
1081 ms
punycode.min.js
1081 ms
utils.min.js
1062 ms
wpforms.min.js
1052 ms
lazyload.min.js
1054 ms
HornBG4.jpg
139 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff
193 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXx-p7K4GLvztg.woff
194 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw2aXx-p7K4GLvztg.woff
195 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXx-p7K4GLvztg.woff
195 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw0aXx-p7K4GLvztg.woff
195 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff
193 ms
font
197 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff
195 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff
196 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff
197 ms
fl-icons.ttf
197 ms
flatsome.js
104 ms
g.gif
110 ms
g.gif
32 ms
locationgreyc.png
34 ms
MHlogo2023b.svg
86 ms
MH3ManualBox.jpg
32 ms
MH3ManualBox2.jpg
38 ms
Replacement1.jpg
30 ms
Replacement5.jpg
36 ms
Replacement6.jpg
55 ms
Replacement4.jpg
64 ms
DTRelayKitPic2.jpg
63 ms
Bags_HomePagePic1.jpg
62 ms
MHHomeThumb7.jpg
80 ms
MHVHomeThumb6.jpg
86 ms
DTHomeThumbMobile6.jpg
106 ms
DTHomeThumbDesktop6.jpg
97 ms
BagsHomeThumbDsktop3.jpg
103 ms
BagsHomeThumbMobile2.jpg
107 ms
MH2p2.jpg
122 ms
MH2p6.jpg
117 ms
MH2p5.jpg
134 ms
MH2p27.jpg
143 ms
MH2p10.jpg
147 ms
MH2p3.jpg
186 ms
MH2p11.jpg
144 ms
MH2p7.jpg
151 ms
MH2p18.jpg
181 ms
MH2p13.jpg
182 ms
MH2p9.jpg
207 ms
MH2p12.jpg
178 ms
MH2p14.jpg
235 ms
MH2p24.jpg
218 ms
MH2p23.jpg
207 ms
MH2p15.jpg
224 ms
MH2p20.jpg
221 ms
MH2p17.jpg
240 ms
MH2p25.jpg
279 ms
MH2p21.jpg
264 ms
Findusonfblogo.svg
226 ms
FooterLogo2023.svg
239 ms
submit-spin.svg
295 ms
loadingAnimation.gif
244 ms
motohorn.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
[aria-hidden="true"] elements contain focusable descendents
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
motohorn.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
motohorn.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Motohorn.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 Motohorn.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.
motohorn.com
Open Graph data is detected on the main page of Moto Horn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: