2.4 sec in total
38 ms
2.2 sec
129 ms
Click here to check amazing Shop VELO content for Pakistan. Otherwise, check out these important facts you probably never knew about shop.velo.com
Enjoy nicotine wherever you go in life with VELO. Nicotine pouches that can be used anywhere. No Hassles. No Tobacco Leaf. No Limits.
Visit shop.velo.comWe analyzed Shop.velo.com page load time and found that the first response time was 38 ms and then it took 2.4 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.
shop.velo.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value9.2 s
1/100
25%
Value7.4 s
27/100
10%
Value2,550 ms
4/100
30%
Value0.125
83/100
15%
Value14.3 s
9/100
10%
38 ms
27 ms
587 ms
317 ms
93 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Shop.velo.com, 22% (17 requests) were made to Velo.com and 4% (3 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Assets.adobedtm.com.
Page size can be reduced by 859.9 kB (73%)
1.2 MB
323.6 kB
In fact, the total size of Shop.velo.com main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 77.1 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 77.1 kB or 82% of the original size.
Potential reduce by 782.9 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 782.9 kB or 72% of the original size.
Number of requests can be reduced by 57 (81%)
70
13
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shop VELO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and as a result speed up the page load time.
www.velo.com
38 ms
isman-To-first-it-Was-there-as-an-his-call-vp-hi
27 ms
resource-cache-service-worker.js
587 ms
polyfill.min.js
317 ms
launch-EN66d1505d231e4d7a8fc8c95533aae9b5.min.js
93 ms
clientlib-dependencies.4e894d7c9c3eb7e656093308b851115f.css
83 ms
clientlib-dependencies.cdec5949bfb95e5e2930ccd59cf9fcb2.css
25 ms
clientlib-all.9629bada8ab7fc7c6586791901ccd543.css
82 ms
clientlib-dependencies.a9dcac4698709ca8e1cbc88363cf0793.js
79 ms
clientlib-dependencies.add75697ab9dc8a84ac97a5e86914a81.js
81 ms
clientlib-all.b50dc7a2d3dad9e3d00ed686be4c28df.js
99 ms
_Incapsula_Resource
93 ms
id
236 ms
AppMeasurement.min.js
89 ms
AppMeasurement_Module_ActivityMap.min.js
168 ms
AppMeasurement_Module_AudienceManagement.min.js
210 ms
2023-VELO-AugustUpdate-LoginBG-V2.jpg
1359 ms
activityi;src=9450401;type=account;cat=accou0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=8545624327380.21
1350 ms
token.json
113 ms
RCed43f9352b6a4d8ba9f46454c49890cb-source.min.js
91 ms
js
1228 ms
RC7892f59dd6354f5da781326276868c3b-source.min.js
69 ms
RC7290f7a86f964730a8203a9b84ac65aa-source.min.js
70 ms
RC07f91ab187d74f5780dfa6c2faf3b383-source.min.js
150 ms
RC8c37ed8ecce34b369744c10f0f4b521b-source.min.js
115 ms
RC793d7e7cc125435a9fd0a78b769b807a-source.min.js
148 ms
RC83b8754087da4aa3b92f4e3867c6f3df-source.min.js
151 ms
RC64ec89522fb94ee4a4fa31bb4ca01387-source.min.js
147 ms
RC02063a72232144678524d72e0c2a137d-source.min.js
149 ms
RC2a70ebedcb404bec9e407fd49be49a22-source.min.js
1202 ms
RCb3a90ce2914e4506ad3e7370b3241834-source.min.js
1202 ms
RC3af31652537d4b5792d971214e9cb93b-source.min.js
1202 ms
RC228bba6dd2294317999dbe82d87e1627-source.min.js
1201 ms
RC2b5377e5f09a4e42b3e8d63891175368-source.min.js
1203 ms
RC6c58392216884028b55b64dbf83dd361-source.min.js
1202 ms
RC08bb2344db004695b2c6da1f727f7fb2-source.min.js
1205 ms
RC065b79f986da44e5a9a57eef90586352-source.min.js
1205 ms
RCaabd43f311de468bae5f22ac65039e76-source.min.js
1204 ms
RCb48b899ab08e42049b8b2d3be9da503c-source.min.js
1204 ms
RC0ff84bda98854f42a10dc3261d9392b5-source.min.js
1274 ms
RC894596c2afc94c1b8e4cea9ec69562ac-source.min.js
1273 ms
RC22e60644e57e4d65999f806234b6f4bf-source.min.js
1273 ms
RCfaa256c8b44e4b9ab63ad9130ad39f54-source.min.js
1273 ms
RC5e469f1381764533b83794fd42050150-source.min.js
1273 ms
RC4e0f909fb4d54ded85319f675ee9b0bb-source.min.js
1271 ms
RC4fcd7c206ddf407086f7684843346581-source.min.js
1355 ms
RCd87f738c3192497abb4eef2e65e68c2d-source.min.js
1355 ms
RC3ace9c039bb84187b65fa205287f3029-source.min.js
1354 ms
RC41b84a958bc94cc2ac524384ef2a22dd-source.min.js
1354 ms
RC715dab8486714067b00ab0815cb00d3b-source.min.js
1353 ms
RC127a2e102b15418baa3b2f36c23446f3-source.min.js
1353 ms
RC887277fd57ab481a8de71c3146e90838-source.min.js
1367 ms
RCe6b12d383e95465f9a3df19f2972230e-source.min.js
1365 ms
RCfdfb38ac257a43ed9ade1b1cfb4f8f16-source.min.js
1366 ms
VELOSans-Regular.otf
63 ms
VELOSans-Bold.otf
132 ms
icomoon_svt348.ttf
63 ms
VELOSans-Medium.otf
96 ms
RC31b287d7dcec465abee84065c99694aa-source.min.js
1358 ms
_Incapsula_Resource
90 ms
RCbc5af7d4f4304e0aadd66d0c1bf3c855-source.min.js
1311 ms
RC127a27f52abf4ebb8bf2d307475a82d2-source.min.js
1309 ms
RC60724203e4c24de3aa20e2e73cb5db35-source.min.js
1316 ms
fbevents.js
1210 ms
RCa89ed6f2d4974af9b36182426f32cb77-source.min.js
1307 ms
dest5.html
1291 ms
RC62dbfd53cc4341a991ac5e3e64671e90-source.min.js
1241 ms
RCb7c9e9e730804537bf6d4773c05d8c8d-source.min.js
1278 ms
RC00021e539b8a4b5b95da330df60ebe20-source.min.js
1235 ms
RCefc0edcd659d42448d34fe86b5c9a404-source.min.js
1234 ms
s96766795313451
194 ms
src=9450401;type=account;cat=accou0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=8545624327380.21
183 ms
104 ms
ibs:dpid=411&dpuuid=Zeo1wgAAAICoeQNP
17 ms
34 ms
ibs:dpid=21&dpuuid=214920604814008493515
8 ms
s99638144276104
25 ms
shop.velo.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.
shop.velo.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
Missing source maps for large first-party JavaScript
shop.velo.com SEO score
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 Shop.velo.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 Shop.velo.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.
shop.velo.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: