5.9 sec in total
382 ms
5.3 sec
281 ms
Click here to check amazing Omnitel content for Lithuania. Otherwise, check out these important facts you probably never knew about omnitel.net
Mobilaus ryšio, interneto ir televizijos paslaugos privatiems klientams. Planai ir įranga pagal jūsų poreikius lanksčiomis mokėjimo sąlygomis. Išsirinkite.
Visit omnitel.netWe analyzed Omnitel.net page load time and found that the first response time was 382 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
omnitel.net performance score
382 ms
547 ms
240 ms
124 ms
371 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Omnitel.net, 57% (47 requests) were made to Omnitel.lt and 11% (9 requests) were made to Trackers.adtarget.me. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Omnitel.lt.
Page size can be reduced by 2.2 MB (61%)
3.6 MB
1.4 MB
In fact, the total size of Omnitel.net main page is 3.6 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. 40% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 121.6 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 37.2 kB, which is 27% 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 121.6 kB or 87% of the original size.
Potential reduce by 6.5 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. Omnitel images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 69% of the original size.
Potential reduce by 943.7 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. Omnitel.net needs all CSS files to be minified and compressed as it can save up to 943.7 kB or 90% of the original size.
Number of requests can be reduced by 56 (77%)
73
17
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omnitel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
omnitel.net
382 ms
privatiems
547 ms
2490540109.js
240 ms
jquery.min.js
124 ms
jquery-ui.min.js
371 ms
oop-liferay-theme.min.js
977 ms
server-side.js
356 ms
listing-component.js
358 ms
aui.css
482 ms
main.css
473 ms
main.css
471 ms
notifications-base.css
469 ms
global-search.css
483 ms
link-phone-number-portlet-base.css
584 ms
mega-menu.css
586 ms
main.css
588 ms
third-level-menu.css
597 ms
oop-feedback-button.css
598 ms
barebone.jsp
1208 ms
oop-ss-notifications-portlet.min.js
702 ms
oop-cm-search-portlet.min.js
704 ms
oop-sm-link-phone-number-portlet.min.js
711 ms
main.js
713 ms
main.js
822 ms
third-level-menu.js
823 ms
main.css
844 ms
oop-base.css
1048 ms
lib-commons.css
948 ms
main.js
939 ms
jquery.elementresize.js
1043 ms
oop-back-to-top.js
1061 ms
td.js
38 ms
j.php
91 ms
browsers.png
313 ms
logo.png
149 ms
logo-alt.png
147 ms
970084cd-ccfe-4d72-81bd-cd7c042c410c
199 ms
3c42aae8-0df5-4b15-a04d-f7e9c309926e
2600 ms
3d3cf3a1-0a53-4ce8-b0b2-eefb1b7f5dc8
458 ms
cc3bcc00-81ef-4670-9997-41385878ac52
433 ms
84dd65ff-81fd-4104-bb99-dd1e738fd5e0
533 ms
open-sans-bold.woff
793 ms
open-sans-regular.woff
751 ms
oop-icons-font.woff
1664 ms
roleId
538 ms
user
605 ms
login-page
643 ms
v.gif
49 ms
helvetica-neue-lt-pro-light.woff
596 ms
588 ms
gtm.js
146 ms
get-products-comparison
606 ms
fontawesome-alloy.woff
689 ms
toolbar
182 ms
analytics.js
78 ms
gtm.js
52 ms
461 ms
fbevents.js
172 ms
gemius.js
605 ms
pixel.min.js
418 ms
collect
21 ms
collect
58 ms
collect
33 ms
collect
65 ms
ga-audiences
58 ms
109 ms
110 ms
fpdata.js
124 ms
lsget.html
511 ms
95 ms
101 ms
99 ms
pixel
37 ms
pixel
20 ms
236 ms
redot.js
131 ms
sync.cgi
671 ms
sync
24 ms
96 ms
96 ms
97 ms
95 ms
97 ms
omnitel.net SEO score
LT
LT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omnitel.net 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 Omnitel.net 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.
omnitel.net
Open Graph description is not detected on the main page of Omnitel. 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: