7.9 sec in total
2.5 sec
5.2 sec
316 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
AUKŠTOJI VALSTYBINĖ MOKYKLA
Visit viko.ltWe analyzed Viko.lt page load time and found that the first response time was 2.5 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
viko.lt performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value14.2 s
0/100
25%
Value9.8 s
10/100
10%
Value130 ms
96/100
30%
Value0.775
5/100
15%
Value10.9 s
21/100
10%
2451 ms
25 ms
242 ms
234 ms
236 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 87% of them (79 requests) were addressed to the original Viko.lt, 3% (3 requests) were made to S.gravatar.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Viko.lt.
Page size can be reduced by 640.9 kB (23%)
2.8 MB
2.2 MB
In fact, the total size of Viko.lt main page is 2.8 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 2.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 80% of the original size.
Potential reduce by 138.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. VIKO images are well optimized though.
Potential reduce by 328.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 328.2 kB or 63% of the original size.
Potential reduce by 97.1 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 97.1 kB or 82% of the original size.
Number of requests can be reduced by 36 (41%)
87
51
The browser has sent 87 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 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.viko.lt
2451 ms
css
25 ms
modernizr.js
242 ms
super-post.css
234 ms
pagenavi-css.css
236 ms
style.css
237 ms
styles.css
236 ms
jetpack.css
354 ms
jquery.js
693 ms
jquery-migrate.min.js
349 ms
jquery.super-post.js
352 ms
jquery.js
469 ms
index.js
249 ms
eventorganiser-front-end.min.css
356 ms
photon.js
356 ms
devicepx-jetpack.js
60 ms
gprofiles.js
53 ms
wpgroho.js
356 ms
wp-embed.min.js
364 ms
qtip2.js
638 ms
core.min.js
474 ms
widget.min.js
476 ms
button.min.js
481 ms
datepicker.min.js
636 ms
moment.min.js
731 ms
fullcalendar.min.js
824 ms
event-manager.min.js
637 ms
frontend.min.js
727 ms
e-201609.js
4 ms
wp-emoji-release.min.js
589 ms
bg.jpg
435 ms
logo.png
147 ms
social_fb.png
197 ms
social_tw.png
205 ms
social_yt.png
209 ms
social_gp.png
434 ms
social_rss.png
435 ms
lang_en.png
435 ms
top_naw.png
436 ms
top_naw2.png
436 ms
loading.gif
437 ms
baneris_rev1.jpg
785 ms
SPFbaneriai.png
1265 ms
ATF-TMP-konferencijos-20160427-baneris.png
1042 ms
viko.lt_.png
1164 ms
baneriui_Q.png
1045 ms
Image2.jpg
1286 ms
Vaizdo_konf_2015.jpg
1014 ms
Baneris.jpg
1151 ms
karjera-.lt_.png
1282 ms
3-way-1.png
440 ms
3-way-2.png
439 ms
3-way-3.png
439 ms
faculty-1.png
440 ms
faculty-2.png
446 ms
faculty-3.png
514 ms
faculty-4.png
567 ms
faculty-5.png
555 ms
faculty-6.png
537 ms
faculty-7.png
538 ms
TRS-20160216_094456-180x124.jpg
543 ms
AKu1CjQ4qnV8MUltkAX3sL-c4ITn5Q_POmZ02hR8-vs.ttf
42 ms
6LmGj5dOJopQKEkt88GowT5B6K9vfp3CayYCLKeg4jg.ttf
90 ms
6LmGj5dOJopQKEkt88GowevaPSzg_gZgeF6JJ43l2YM.ttf
91 ms
pirma-foto-180x124.jpg
584 ms
P2252763-e1456490253965-180x124.jpg
558 ms
2016-02-25_4-180x124.jpg
560 ms
20160214_113308-1-180x124.jpg
535 ms
baner_widget_1.png
543 ms
baner_widget_2.png
494 ms
baner_widget_3.png
636 ms
baner_widget_12.png
583 ms
ga.js
30 ms
g.gif
4 ms
mswin10.png
569 ms
hovercard.css
41 ms
services.css
67 ms
__utm.gif
23 ms
asso_eurashe.png
361 ms
asso_enphe.png
374 ms
asso_cdio.png
376 ms
asso_space.png
473 ms
vetnet.png
475 ms
ComeniusLogoviko.png
478 ms
uasnet_viko.png
489 ms
logo_sm.png
490 ms
arrows.simple.png
516 ms
bg_menu.jpg
583 ms
six_right.png
586 ms
date.png
581 ms
more.png
527 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
Tap targets are not sized appropriately
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 data is detected on the main page of VIKO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: