Access bugy.sk. Najväčšia online drogéria Bugy.sk - super ceny - rýchle dodanie | Bugy.sk

bugy.sk screenshot

14

Performance

Renders faster than
26% of other websites
73

Accessibility

Visual factors better than
that of 38% of websites
75

Best Practices

More advanced features
available than in
35% of websites
99

SEO

Google-friendlier than
93% of websites

First Response

286 ms

Resources Loaded

3.9 sec

Page Rendered

317 ms

bugy.sk screenshot

About Website

Visit bugy.sk now to see the best up-to-date Bugy content for Slovakia and also check out these interesting facts you probably never knew about bugy.sk

Už sa Vám nechce chodiť do obchodu a strácať čas zdĺhavým nakupovaním? Vyskúšajte si nákup v online drogérii Bugy, kde nájdete viac než 9 000 značkových výrobkov skladom z drogerie, parfumérie, kozmet...

Visit bugy.sk

Key Findings

We analyzed Bugy.sk page load time and found that the first response time was 286 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value2,230 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.709

7/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

bugy.sk

286 ms

bugy.sk

747 ms

gtm.js

105 ms

fbevents.js

59 ms

sm.js

954 ms

Our browser made a total of 174 requests to load all elements on the main page. We found that 82% of them (142 requests) were addressed to the original Bugy.sk, 3% (6 requests) were made to Cdnjs.cloudflare.com and 3% (5 requests) were made to Salesmanago.pl. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Bugy.sk.

Content Size

1.5 MB

After Optimization

1.3 MB

In fact, the total size of Bugy.sk main page is 1.5 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 138.3 kB

Original 161.3 kB
After minification 118.7 kB
After compression 23.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.6 kB, which is 26% 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 138.3 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 28.5 kB

Original 1.0 MB
After minification 998.4 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. Bugy images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.5 kB

Original 281.1 kB
After minification 281.1 kB
After compression 273.6 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.

CSS Optimization

-1%

Potential reduce by 202 B

Original 24.6 kB
After minification 24.6 kB
After compression 24.4 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. Bugy.sk has all CSS files already compressed.

Requests Now

168

After Optimization

131

The browser has sent 168 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bugy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Some elements have a [tabindex] value greater than 0

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

SK
Language Claimed

SK
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bugy.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that Bugy.sk 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.

Social Sharing Optimization

bugy.sk

Open Graph description is not detected on the main page of Bugy. 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: