18.2 sec in total
44 ms
17.6 sec
595 ms
Click here to check amazing High Que content. Otherwise, check out these important facts you probably never knew about high-que.com
Visit Kick Ash Basket to learn about the spark that started it all on our about us page. We love to share our story with our Kick Ash family and friends!
Visit high-que.comWe analyzed High-que.com page load time and found that the first response time was 44 ms and then it took 18.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
high-que.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value13.5 s
0/100
25%
Value6.7 s
36/100
10%
Value1,450 ms
15/100
30%
Value0.229
54/100
15%
Value17.1 s
4/100
10%
44 ms
291 ms
69 ms
22 ms
55 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original High-que.com, 65% (80 requests) were made to Kickashbasket.com and 7% (8 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (15.8 sec) relates to the external source Gtmfsstatic.getgoogletagmanager.com.
Page size can be reduced by 1.2 MB (36%)
3.3 MB
2.1 MB
In fact, the total size of High-que.com main page is 3.3 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 224.8 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. This page needs HTML code to be minified as it can gain 50.8 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 224.8 kB or 80% of the original size.
Potential reduce by 920.2 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, High Que needs image optimization as it can save up to 920.2 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 51.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 51.8 kB or 16% of the original size.
Potential reduce by 1.3 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. High-que.com has all CSS files already compressed.
Number of requests can be reduced by 86 (74%)
116
30
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of High Que. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
high-que.com
44 ms
high-que
291 ms
gtm.js
69 ms
core.js
22 ms
preloads.js
55 ms
load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js
45 ms
storefront-a2d444786d996da5634fbbaeeffe6104ee672440dfa6cdcaebfb27dceaaf9c0f.js
43 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
44 ms
styles.css
47 ms
scripts.js
46 ms
irina.js
61 ms
main-nav.css
59 ms
shop-by-brand.css
60 ms
brand-collection.css
56 ms
baskets-collection.css
57 ms
product-page.css
95 ms
irina-cart.css
97 ms
pages.css
99 ms
irina.css
98 ms
custom.css
95 ms
core.css
100 ms
button.css
102 ms
grid.css
103 ms
media.css
104 ms
hero.css
131 ms
price.css
105 ms
slick.css
43 ms
jquery-3.6.0.min.js
44 ms
slick.min.js
47 ms
js
101 ms
js
159 ms
klaviyo.js
47 ms
announcement-bar.css
103 ms
main-header.css
167 ms
main-header-sticky.js
156 ms
predictive-search-input.js
158 ms
main-navigation.css
159 ms
main-navigation.js
158 ms
main-header.js
160 ms
cart-counter.js
160 ms
form.css
160 ms
newsletter.css
163 ms
floating-content.css
163 ms
newsletter-click.js
201 ms
page-header.css
173 ms
localization-selector.js
275 ms
newsletter-customer-posted.js
254 ms
modal.js
250 ms
cart.js
250 ms
animation-section-reveal.js
250 ms
custom.js
250 ms
js
175 ms
js
155 ms
trekkie.storefront.a0a07daed3df64bc141ebd704f9608fcc6496227.min.js
149 ms
shop_events_listener-a7c63dba65ccddc484f77541dc8ca437e60e1e9e297fe1c3faebf6523a0ede9b.js
148 ms
shopify-boomerang-1.0.0.min.js
146 ms
fb-white.svg
434 ms
logo.png
146 ms
gift_600x.jpg
141 ms
WuhVoKly_600x.jpg
146 ms
4bY69EYA_600x.jpg
625 ms
Gasket_600x.png
473 ms
shutterstock_1983163565_600x.png
509 ms
home-gif2_600x.gif
605 ms
pin-white.svg
461 ms
insa-white.svg
460 ms
yt-white.svg
459 ms
fender_analytics.21a5e7f7e70af502c5ee.js
453 ms
static.047f24ade89e4aff54a9.js
456 ms
runtime.47052cf3dd870ea5c769.js
187 ms
sharedUtils.8212819f5b89555febe8.js
419 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js
419 ms
vendors~signup_forms.2c2f6e8ccec13e3b6caf.js
419 ms
signup_forms.ee5c5274d631fa53e391.js
420 ms
grunge_one.png
462 ms
dark-grunge.png
538 ms
line_two.png
467 ms
insta1_260x260@2x.jpg
675 ms
insta2_260x260@2x.jpg
466 ms
insta3_260x260@2x.jpg
467 ms
insta4_260x260@2x.jpg
503 ms
insta5_260x260@2x.jpg
539 ms
249 ms
js
179 ms
montserrat_n7.78b0223375c94b39ce1af7e09a0225f2bb3d05f7.woff
257 ms
montserrat_n4.cfce41a967758ce5a9b7d48daeb5b028fd977a9b.woff
275 ms
ZuumeRough-Bold.woff
179 ms
Bernierdistressed.woff
180 ms
stylepower-webfont.woff
207 ms
analytics.js
58 ms
52 ms
collect
38 ms
collect
14 ms
ga-audiences
15 ms
spinner.css
17 ms
spinner.css
12 ms
animation-section-reveal.css
14 ms
animation-section-reveal.css
16 ms
cart-counter.css
16 ms
cart-counter.css
15 ms
main-header-sticky.css
17 ms
main-header-sticky.css
15 ms
search-popup.css
14 ms
predictive-search-input.css
144 ms
gallery-card.css
16 ms
gallery-card.css
14 ms
main-footer.css
16 ms
main-footer.css
13 ms
modal.css
15 ms
modal.css
19 ms
loader.js
97 ms
loader.js
169 ms
script.js
94 ms
hello.js
40 ms
gtmfsv2.js
15772 ms
hello.js
3 ms
country
186 ms
cart.json
60 ms
spr-0e683603bfa450170bff33e7fbad64e7dfe9585e1caeb951bbe283e5a2306523.js
16 ms
spr-07102fd76ff4bc22a3e0c32f0cca9ee51c77c34bbc4bdac79abb48f698de10dd.css
19 ms
jquery.min.js
22 ms
translation
53 ms
US.png
8 ms
high-que.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
high-que.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
Page has valid source maps
high-que.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 High-que.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 High-que.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.
high-que.com
Open Graph data is detected on the main page of High Que. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: