4 sec in total
416 ms
3.1 sec
441 ms
Visit viko.lt now to see the best up-to-date VIKO content for Lithuania and also check out these interesting facts you probably never knew about viko.lt
Visit viko.ltWe analyzed Viko.lt page load time and found that the first response time was 416 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
viko.lt performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value11.6 s
0/100
25%
Value9.6 s
11/100
10%
Value800 ms
36/100
30%
Value0.775
5/100
15%
Value11.6 s
18/100
10%
416 ms
372 ms
916 ms
275 ms
273 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 82% of them (51 requests) were addressed to the original Viko.lt, 8% (5 requests) were made to Cdnjs.cloudflare.com and 3% (2 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (916 ms) belongs to the original domain Viko.lt.
Page size can be reduced by 472.6 kB (20%)
2.4 MB
1.9 MB
In fact, the total size of Viko.lt main page is 2.4 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.9 MB which makes up the majority of the site volume.
Potential reduce by 94.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 94.0 kB or 86% of the original size.
Potential reduce by 106.0 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. VIKO images are well optimized though.
Potential reduce by 99.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 99.2 kB or 68% of the original size.
Potential reduce by 173.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. Viko.lt needs all CSS files to be minified and compressed as it can save up to 173.4 kB or 86% of the original size.
Number of requests can be reduced by 25 (46%)
54
29
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VIKO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
viko.lt
416 ms
viko.lt
372 ms
www.viko.lt
916 ms
style.min.css
275 ms
cookie-law-info-public.css
273 ms
cookie-law-info-gdpr.css
363 ms
bootstrap.min.css
44 ms
css2
44 ms
style.css
452 ms
lightgallery-bundle.min.css
40 ms
lightslider.min.css
64 ms
jquery.min.js
462 ms
jquery-migrate.min.js
279 ms
cookie-law-info-public.js
451 ms
js
81 ms
js
120 ms
piano.min.js
102 ms
cookie-law-info-table.css
364 ms
bootstrap.bundle.min.js
36 ms
lightgallery.min.js
60 ms
lightslider.min.js
61 ms
wow.min.js
59 ms
scripts.js
364 ms
logo-white-lt.png
142 ms
logo-mobile.svg
141 ms
FB-cover2024_01-scaled.jpg
284 ms
img-rectangle.svg
138 ms
FB-meniu-ikona_zalia2.jpg
142 ms
FB-meniu-ikona_zalia4.jpg
141 ms
FB-meniu-ikona2.jpg
281 ms
FB-meniu-ikona_zalia3.jpg
280 ms
FB-meniu-ikona3.jpg
279 ms
img-people.jpg
281 ms
icon-arrow-white.png
280 ms
icon-arrow-green.png
282 ms
cover-fiziniai.jpg
458 ms
cover-informatikos.jpg
409 ms
cover-menai.jpg
456 ms
cover-sveikatos.jpg
545 ms
cover-ugdymo.jpg
368 ms
cover-veterinarijos.jpg
458 ms
cover-humanitariniai.jpg
550 ms
cover-inzineriniai.jpg
681 ms
cover-socialiniai.jpg
726 ms
cover-technologiju.jpg
639 ms
cover-verslo.jpg
550 ms
cover-ukio.jpg
636 ms
logo-blue-lt.png
641 ms
icon-facebook.png
642 ms
icon-instagram.png
727 ms
icon-youtube.png
730 ms
icon-linkedin.png
731 ms
icon-arrow-top.png
732 ms
AzoSans-Medium.woff
603 ms
AzoSans-Regular.woff
649 ms
AzoSans-Light.woff
659 ms
AzoSans-Thin.woff
660 ms
AzoSans-Bold.woff
662 ms
bg-01.svg
551 ms
bg-02.svg
585 ms
bg-03.svg
633 ms
bg-04.svg
630 ms
viko.lt accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
viko.lt 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
Page has valid source maps
viko.lt 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
LT
LT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viko.lt can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian is used on the page, and it matches the claimed language. Our system also found out that Viko.lt 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.
viko.lt
Open Graph description is not detected on the main page of VIKO. 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: