3.6 sec in total
245 ms
2.5 sec
856 ms
Click here to check amazing Viobin content. Otherwise, check out these important facts you probably never knew about viobin.com
Visit viobin.comWe analyzed Viobin.com page load time and found that the first response time was 245 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
viobin.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value18.2 s
0/100
25%
Value8.3 s
19/100
10%
Value1,890 ms
9/100
30%
Value0.015
100/100
15%
Value25.3 s
0/100
10%
245 ms
361 ms
41 ms
146 ms
48 ms
Our browser made a total of 195 requests to load all elements on the main page. We found that 88% of them (171 requests) were addressed to the original Viobin.com, 5% (9 requests) were made to Fonts.gstatic.com and 3% (6 requests) were made to Scontent-iad3-2.cdninstagram.com. The less responsive or slowest element that took the longest time to load (605 ms) belongs to the original domain Viobin.com.
Page size can be reduced by 229.1 kB (7%)
3.1 MB
2.8 MB
In fact, the total size of Viobin.com main page is 3.1 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 168.7 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 168.7 kB or 83% of the original size.
Potential reduce by 60.3 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. Viobin images are well optimized though.
Potential reduce by 79 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 88 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. Viobin.com needs all CSS files to be minified and compressed as it can save up to 88 B or 23% of the original size.
Number of requests can be reduced by 144 (86%)
167
23
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viobin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 92 to 1 for JavaScripts and from 54 to 1 for CSS and as a result speed up the page load time.
viobin.com
245 ms
viobin.com
361 ms
wc-square-cart-checkout-blocks.min.css
41 ms
theme.min.css
146 ms
style.css
48 ms
bew-font-icons.min.css
209 ms
third-party.min.css
206 ms
vtprd-front-end-min.css
197 ms
style.css
64 ms
font-awesome.min.css
73 ms
simple-line-icons.min.css
89 ms
bew-woocommerce.css
155 ms
style.css
116 ms
woocommerce-layout.css
140 ms
woocommerce.css
167 ms
style.css
172 ms
frontend.min.css
183 ms
style.min.css
191 ms
header-footer.min.css
188 ms
all.min.css
210 ms
v4-shims.min.css
219 ms
public.css
221 ms
frontend.css
215 ms
jetwoobuilder-frontend-font.css
224 ms
mediaelementplayer-legacy.min.css
276 ms
photoswipe.min.css
312 ms
default-skin.min.css
273 ms
jet-woo-product-gallery.css
240 ms
elementor-icons.min.css
239 ms
frontend.min.css
304 ms
swiper.min.css
261 ms
post-32.css
263 ms
frontend.min.css
287 ms
wpforms-full.min.css
313 ms
frontend.min.css
345 ms
all.min.css
317 ms
v4-shims.min.css
324 ms
css
45 ms
post-4906.css
369 ms
post-11162.css
297 ms
post-4900.css
283 ms
ptp-combined.min.css
325 ms
chosen.min.css
273 ms
jet-search.css
288 ms
woocommerce.css
266 ms
jquery.fancybox.min.css
272 ms
frontend.min.css
249 ms
fontawesome.min.css
226 ms
solid.min.css
256 ms
brands.min.css
265 ms
wc-blocks.css
269 ms
pp-woocommerce.min.css
279 ms
post-2601.css
212 ms
hamburgers.min.css
235 ms
jquery.min.js
253 ms
jquery-migrate.min.js
293 ms
imagesloaded.min.js
254 ms
jquery.blockUI.min.js
281 ms
add-to-cart.min.js
289 ms
js.cookie.min.js
245 ms
woocommerce.min.js
455 ms
woo-stamped.io-public.js
241 ms
v4-shims.min.js
248 ms
public.js
243 ms
jquery.fancybox.min.js
251 ms
bew-general.js
504 ms
third-party-scripts.min.js
499 ms
underscore.min.js
475 ms
wp-util.min.js
464 ms
bew-shortcodes.js
458 ms
chosen.jquery.min.js
458 ms
jet-plugins.js
455 ms
jet-search.js
453 ms
dynamic-conditions-public.js
482 ms
sourcebuster.min.js
481 ms
order-attribution.min.js
467 ms
wp-polyfill-inert.min.js
440 ms
regenerator-runtime.min.js
449 ms
wp-polyfill.min.js
443 ms
react.min.js
545 ms
hooks.min.js
545 ms
deprecated.min.js
543 ms
dom.min.js
531 ms
react-dom.min.js
486 ms
escape-html.min.js
479 ms
element.min.js
507 ms
is-shallow-equal.min.js
506 ms
i18n.min.js
571 ms
keycodes.min.js
535 ms
priority-queue.min.js
556 ms
compose.min.js
558 ms
private-apis.min.js
554 ms
redux-routine.min.js
554 ms
data.min.js
541 ms
lodash.min.js
552 ms
wc-blocks-registry.js
553 ms
widget.min.js
275 ms
url.min.js
576 ms
api-fetch.min.js
598 ms
wc-settings.js
605 ms
hotjar-2422916.js
400 ms
universal.js
322 ms
380884584_799665081842664_3978591650345866541_n.jpg
279 ms
357641745_600097305639752_169745809302516621_n.jpg
279 ms
378202645_804672698330860_4561525800315985336_n.jpg
254 ms
356207527_800346571590393_340533035964488015_n.jpg
296 ms
353599431_271313322055110_7633552514583868178_n.jpg
295 ms
350247853_1003068587671329_1175472787985918880_n.jpg
297 ms
346861529_5629529353813352_84184468108226024_n.jpg
366 ms
348255450_1987934881548499_1626450849547972873_n.jpg
340 ms
data-controls.min.js
405 ms
html-entities.min.js
305 ms
notices.min.js
298 ms
wc-blocks-middleware.js
320 ms
wc-blocks-data.js
327 ms
dom-ready.min.js
332 ms
a11y.min.js
447 ms
primitives.min.js
342 ms
warning.min.js
349 ms
blocks-components.js
399 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
70 ms
pxiByp8kv8JHgFVrLFj_Z1xlEw.woff
109 ms
pxiGyp8kv8JHgFVrLPTucHtG.woff
148 ms
pxiEyp8kv8JHgFVrJJfedA.woff
177 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
177 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
179 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
178 ms
pxiByp8kv8JHgFVrLDD4Z1xlEw.woff
177 ms
pxiByp8kv8JHgFVrLBT5Z1xlEw.woff
179 ms
blocks-checkout.js
365 ms
order-attribution-blocks.min.js
366 ms
api-request.min.js
332 ms
frontend.min.js
355 ms
vue.min.js
353 ms
jet-menu-public-scripts.js
360 ms
universal.css
77 ms
ptp-combined.min.js
353 ms
frontend.min.js
362 ms
make-column-clickable.js
278 ms
jquery.smartmenus.min.js
326 ms
frontend-mini-cart.min.js
309 ms
pp-woocommerce.min.js
308 ms
woo-general.js
359 ms
frontend-offcanvas-content.min.js
321 ms
modules.a4fd7e5489291affcf56.js
70 ms
imagesloaded.min.js
237 ms
isotope.min.js
287 ms
jquery.magnific-popup.min.js
284 ms
swiper.min.js
255 ms
frontend.min.js
254 ms
webpack-pro.runtime.min.js
253 ms
webpack.runtime.min.js
294 ms
frontend-modules.min.js
251 ms
frontend.min.js
301 ms
waypoints.min.js
319 ms
core.min.js
250 ms
frontend.min.js
300 ms
elements-handlers.min.js
293 ms
widgets-scripts.js
239 ms
frontend.min.js
257 ms
jquery.sticky.min.js
272 ms
frontend.min.js
318 ms
tooltipster.min.js
284 ms
Raleway-Regular.ttf
393 ms
Raleway-Medium.ttf
381 ms
Raleway-Light.ttf
423 ms
Raleway-ExtraLight.ttf
345 ms
Raleway-Thin.ttf
397 ms
Raleway-SemiBold.ttf
340 ms
Raleway-Bold.ttf
392 ms
Raleway-ExtraBold.ttf
390 ms
Raleway-Black.ttf
423 ms
fa-solid-900.woff
448 ms
fa-solid-900.woff
414 ms
fa-solid-900.woff
464 ms
fa-regular-400.woff
401 ms
fa-regular-400.woff
453 ms
AXIS-ExtraBold.ttf
453 ms
fa-brands-400.woff
509 ms
fa-brands-400.woff
569 ms
Viobin-Logo-220x60-1.png
503 ms
home-page-hero.jpg
484 ms
products-oils-tile.jpg
428 ms
products-ingredients-tile.jpg
486 ms
products-animal-nutrition-tile.jpg
469 ms
products-cbd-tile.jpg
521 ms
Bottling-home-page-banner.jpg
519 ms
home-page-store-hero.jpg
445 ms
REX-home-hero-mobile-flipped.jpg
506 ms
wholesale-cbd-hero-mobile.jpg
491 ms
cbd-mocktail-thumbnail.jpg
492 ms
viobin-wheat-germ-oil-for-hair-care.jpg
471 ms
viobin-logo-white-orange-small.png
503 ms
woocommerce-smallscreen.css
23 ms
ga159yle
33 ms
viobin.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.
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
Links do not have a discernible name
viobin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
viobin.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Viobin.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 Viobin.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.
viobin.com
Open Graph description is not detected on the main page of Viobin. 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: