2.5 sec in total
16 ms
2 sec
559 ms
Visit reggaeking.com now to see the best up-to-date REGGAE KING content and also check out these interesting facts you probably never knew about reggaeking.com
Visit reggaeking.comWe analyzed Reggaeking.com page load time and found that the first response time was 16 ms and then it took 2.5 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.
reggaeking.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value6.6 s
8/100
25%
Value10.9 s
6/100
10%
Value2,320 ms
5/100
30%
Value0.001
100/100
15%
Value11.8 s
17/100
10%
16 ms
877 ms
71 ms
92 ms
69 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Reggaeking.com, 45% (31 requests) were made to Cdn11.bigcommerce.com and 10% (7 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (991 ms) relates to the external source Cdn11.bigcommerce.com.
Page size can be reduced by 542.0 kB (13%)
4.3 MB
3.7 MB
In fact, the total size of Reggaeking.com main page is 4.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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 210.0 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 42.1 kB, which is 17% 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 210.0 kB or 84% of the original size.
Potential reduce by 328.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. REGGAE KING images are well optimized though.
Potential reduce by 3.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 63 B
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. Reggaeking.com has all CSS files already compressed.
Number of requests can be reduced by 32 (51%)
63
31
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of REGGAE KING. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
reggaeking.com
16 ms
877 ms
gtm.js
71 ms
theme-bundle.head_async.js
92 ms
css
69 ms
theme-34688000-8bab-013c-4b7e-1ede2c21228e.css
96 ms
js
62 ms
js
144 ms
google_analytics4.js
62 ms
loader.js
90 ms
klaviyo.js
90 ms
index.js
117 ms
04b6b9860a.js
344 ms
05436b6afef9fa19ebf5c85429f0ab06.js
240 ms
theme-bundle.main.js
119 ms
csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js
82 ms
visitor_stencil.js
81 ms
smile-bigcommerce.js
242 ms
fbevents.js
237 ms
analytics.js
206 ms
jquery.min.js
222 ms
visit
191 ms
x
218 ms
clickstream
217 ms
fender_analytics.8b21fd7cc915ea15c535.js
196 ms
static.047f24ade89e4aff54a9.js
196 ms
runtime.7d53bcb31ee7ad2422be.js
94 ms
sharedUtils.dd5b9aaeade0ef8bcc99.js
165 ms
vendors~signup_forms~post_identification_sync~web_personalization~reviews~atlas.3ee75b12730991c4d04b.js
165 ms
vendors~signup_forms~atlas.a79ea752817098cd5ff8.js
174 ms
vendors~signup_forms.5e09daf13e2db724557a.js
174 ms
signup_forms.5e2fea62c24ac2108007.js
173 ms
freeshipping50-2020.jpg
145 ms
cart-grey.png
155 ms
vpreggae_logo_new_logo_1_1704206603__07078.original.png
145 ms
reggaeking__72453.original.jpg
246 ms
BACKPACK_BOB_-LION_RED__86674.1703190589.png
513 ms
BACKPACK_PORTRAIT__21819.1703191651.png
514 ms
BACKPACK_ONE_LOVE__58294.1703192386.png
516 ms
ONE_LOVE_POM_BEANIE.1__10989.1703173554.png
533 ms
BOB_FACE_BEANIE__33908.1703173732.png
535 ms
ONE_LOVE_BEANIE__15361.1703173981.png
534 ms
REBEL_MUSIC__23697.1701902605.png
730 ms
BMTSM0010_LEGEND__78032.1701707194.png
933 ms
BMTSM009_JERSEY__11360.1701706625.png
886 ms
BMTSM007_LIVE__16370.1701706684.png
812 ms
BMTSM006_ROOTS_ROCK__49659.1701706728.png
991 ms
BMTSM005_BOB__13111.1701706773.png
895 ms
americanexpress-logo.png
749 ms
discover-logo.png
768 ms
mastercard-icon.png
788 ms
paypal-logo-png.png
817 ms
visa-card-icon.png
835 ms
amzon-pay-logo.png
834 ms
apple-pay-logo.png
851 ms
ecommerce.js
159 ms
collect
152 ms
04b6b9860a.css
127 ms
05436b6afef9fa19ebf5c85429f0ab06.css
39 ms
nobot
161 ms
collect
23 ms
font-awesome-css.min.css
43 ms
ga-audiences
136 ms
elc
33 ms
index.php
115 ms
fontawesome-webfont.woff
87 ms
theme-bundle.chunk.0.js
326 ms
theme-bundle.chunk.10.js
334 ms
icon-sprite.svg
306 ms
reggaeking.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 IDs are not unique
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
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.
reggaeking.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
reggaeking.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Reggaeking.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 Reggaeking.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.
reggaeking.com
Open Graph description is not detected on the main page of REGGAE KING. 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: