2.3 sec in total
32 ms
2 sec
345 ms
Click here to check amazing Vii content for Slovakia. Otherwise, check out these important facts you probably never knew about vii.sk
Pozrite si videá, relácie a podcasty z produkcie SME a našich partnerov. Na webe nájdete spravodajstvo, rozhovory, publicistiku a zábavu.
Visit vii.skWe analyzed Vii.sk page load time and found that the first response time was 32 ms and then it took 2.3 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.
vii.sk performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value6.2 s
11/100
25%
Value5.9 s
48/100
10%
Value1,100 ms
24/100
30%
Value0.03
100/100
15%
Value12.7 s
14/100
10%
32 ms
713 ms
50 ms
85 ms
101 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Vii.sk, 50% (35 requests) were made to M.smedata.sk and 43% (30 requests) were made to Artemis.smedata.sk. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source M.smedata.sk.
Page size can be reduced by 486.0 kB (23%)
2.1 MB
1.6 MB
In fact, the total size of Vii.sk main page is 2.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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 452.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. 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 452.0 kB or 80% of the original size.
Potential reduce by 0 B
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. Vii images are well optimized though.
Potential reduce by 33.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 33.9 kB or 14% of the original size.
Number of requests can be reduced by 25 (40%)
63
38
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vii. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
vii.sk
32 ms
video.sme.sk
713 ms
consent_gfc.js
50 ms
runtime.fb27fd0c.js
85 ms
7098.42637451.js
101 ms
5045.cd609dc7.js
106 ms
6306.bdf5835a.js
103 ms
8674.d2acc8d0.js
102 ms
5382.74b7badf.js
99 ms
285.51192c33.js
103 ms
1488.0d955ed1.js
112 ms
5948.3d90c713.js
119 ms
sme_general.189605ec.js
115 ms
corpbar_ext.js
72 ms
svg-sprite-call.min.js
140 ms
8757881_640x360.jpg
262 ms
8753272_640x360.jpg
265 ms
8374226_300x200.png
438 ms
8089889_300x200.png
416 ms
8441889_300x200.png
401 ms
7019453_300x200.png
516 ms
6995341_300x200.png
437 ms
8691638_300x200.png
393 ms
7652743_300x200.png
509 ms
8482656_300x200.png
528 ms
7855146_300x200.jpg
547 ms
5384032.png
557 ms
5384612.png
572 ms
5384609.png
627 ms
opensans-regular-webfont.woff
98 ms
greta-display-medium.woff
82 ms
opensans-bold-webfont.woff
112 ms
greta-light-normal.woff
113 ms
8754884_640x360.jpg
625 ms
8754499_640x360.jpg
520 ms
8764207_640x360.jpg
652 ms
8761397_640x360.jpg
661 ms
8753272_320x180.jpg
659 ms
8757881_320x180.jpg
682 ms
8736194_320x180.jpg
716 ms
8754499_320x180.jpg
757 ms
8754884_320x180.jpg
910 ms
8764207_320x180.jpg
793 ms
8742926_320x180.png
699 ms
8761397_320x180.jpg
806 ms
8743129_320x180.jpg
1127 ms
8758606_320x180.jpg
841 ms
8733398_320x180.jpg
883 ms
8742926_640x360.png
1101 ms
8733398_640x360.jpg
1199 ms
7069373_640x360.jpeg
951 ms
4019744_640x360.png
1167 ms
8712087_640x360.jpg
929 ms
8706305_640x360.jpg
1082 ms
fedra-display-heavy.woff
100 ms
jquery-2.2.4.min.js
63 ms
sme_redaction_menu_ajax.c33c78a8.js
73 ms
artemis-additional.min.js
63 ms
3469.3a776167.js
73 ms
2368.edc347a0.js
74 ms
4520.f8601491.js
98 ms
sme_additional.5497b594.js
97 ms
artemis-anltcs.v3.min.js
96 ms
sme_analytics.4cad271f.js
97 ms
modal_dialog.js
30 ms
autocomplete.min.js
98 ms
autocomplete-config.js
98 ms
flickity-video.all.min.js
98 ms
weather-svg-sprite.svg
138 ms
svg-sprite.svg
48 ms
vii.sk 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.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
vii.sk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
vii.sk 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
SK
SK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vii.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 Vii.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.
vii.sk
Open Graph data is detected on the main page of Vii. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: