2.2 sec in total
16 ms
1.6 sec
616 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 16 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
high-que.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value20.2 s
0/100
25%
Value12.1 s
4/100
10%
Value1,470 ms
14/100
30%
Value0.22
57/100
15%
Value40.3 s
0/100
10%
16 ms
153 ms
102 ms
72 ms
39 ms
Our browser made a total of 94 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, 81% (76 requests) were made to Kickashbasket.com and 10% (9 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (579 ms) relates to the external source Kickashbasket.com.
Page size can be reduced by 1.2 MB (34%)
3.4 MB
2.3 MB
In fact, the total size of High-que.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. Only a small number of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 206.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. This page needs HTML code to be minified as it can gain 49.6 kB, which is 20% 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 206.3 kB or 83% of the original size.
Potential reduce by 957.8 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 957.8 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 485 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.
Potential reduce by 1.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. High-que.com has all CSS files already compressed.
Number of requests can be reduced by 67 (77%)
87
20
The browser has sent 87 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 30 to 1 for JavaScripts and from 39 to 1 for CSS and as a result speed up the page load time.
high-que.com
16 ms
high-que
153 ms
gtm.js
102 ms
lo.js
72 ms
core.js
39 ms
preloads.js
70 ms
load_feature-f4e7948c1c9e4f45ef404dbb8b5dbcaa265bad73ea228bf111efe71177b448d9.js
60 ms
storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js
75 ms
scripts.js
87 ms
irina.js
94 ms
main-nav.css
84 ms
shop-by-brand.css
93 ms
brand-collection.css
110 ms
baskets-collection.css
112 ms
product-page.css
111 ms
irina-cart.css
138 ms
pages.css
136 ms
irina.css
120 ms
custom.css
121 ms
core.css
125 ms
button.css
132 ms
grid.css
164 ms
media.css
143 ms
hero.css
144 ms
price.css
158 ms
slick.css
61 ms
jquery-3.6.0.min.js
62 ms
slick.min.js
64 ms
js
105 ms
omnisend-in-shop.js
112 ms
shopify-perf-kit-1.0.0.min.js
211 ms
announcement-bar.css
205 ms
main-header.css
204 ms
main-header-sticky.js
202 ms
predictive-search-input.js
208 ms
main-navigation.css
204 ms
main-navigation.js
204 ms
main-header.js
204 ms
cart-counter.js
219 ms
form.css
221 ms
newsletter.css
210 ms
klaviyo.js
59 ms
page-header.css
212 ms
floating-content.css
256 ms
localization-selector.js
249 ms
newsletter-customer-posted.js
229 ms
modal.js
207 ms
cart.js
251 ms
animation-section-reveal.js
195 ms
custom.js
199 ms
trekkie.storefront.c1258b47cccb7bc2aeeaeb253b8999e078bd2f6b.min.js
134 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
134 ms
shopify-boomerang-1.0.0.min.js
134 ms
fb-white.svg
37 ms
logo.png
132 ms
gift_600x.jpg
130 ms
4bY69EYA_600x.jpg
579 ms
Gasket_600x.png
412 ms
shutterstock_1983163565_600x.png
521 ms
home-gif2_600x.gif
284 ms
pin-white.svg
71 ms
insa-white.svg
71 ms
yt-white.svg
73 ms
montserrat_n7.78b0223375c94b39ce1af7e09a0225f2bb3d05f7.woff
76 ms
montserrat_n4.cfce41a967758ce5a9b7d48daeb5b028fd977a9b.woff
93 ms
ZuumeRough-Bold.woff
53 ms
grunge_one.png
85 ms
dark-grunge.png
112 ms
line_two.png
170 ms
insta1_260x260@2x.jpg
172 ms
insta2_260x260@2x.jpg
172 ms
insta3_260x260@2x.jpg
174 ms
insta4_260x260@2x.jpg
175 ms
insta5_260x260@2x.jpg
178 ms
Bernierdistressed.woff
66 ms
Awesomespill-Regular.otf
41 ms
launcher-v2.js
54 ms
spinner.css
28 ms
spinner.css
21 ms
animation-section-reveal.css
27 ms
animation-section-reveal.css
28 ms
cart-counter.css
30 ms
cart-counter.css
25 ms
main-header-sticky.css
25 ms
main-header-sticky.css
19 ms
search-popup.css
28 ms
predictive-search-input.css
22 ms
gallery-card.css
24 ms
gallery-card.css
20 ms
main-footer.css
24 ms
main-footer.css
23 ms
modal.css
25 ms
modal.css
43 ms
loader.js
55 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: