3.8 sec in total
724 ms
2.7 sec
387 ms
Click here to check amazing OZAS content for Belarus. Otherwise, check out these important facts you probably never knew about ozas.lt
Prekybos ir pramogų centras OZAS Vilniuje – beveik 200 parduotuvių, platus pramogų pasirinkimas, kinas, baseinas ir beveik viskas, ko gali prireikti! Užsuk!
Visit ozas.ltWe analyzed Ozas.lt page load time and found that the first response time was 724 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ozas.lt performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value21.1 s
0/100
25%
Value12.5 s
3/100
10%
Value1,640 ms
11/100
30%
Value0.073
96/100
15%
Value15.5 s
7/100
10%
724 ms
74 ms
174 ms
254 ms
374 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 53% of them (26 requests) were addressed to the original Ozas.lt, 37% (18 requests) were made to Cms.ozas.lt and 4% (2 requests) were made to Cdn.userway.org. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cms.ozas.lt.
Page size can be reduced by 116.5 kB (13%)
904.6 kB
788.1 kB
In fact, the total size of Ozas.lt main page is 904.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 737.5 kB which makes up the majority of the site volume.
Potential reduce by 96.9 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 96.9 kB or 79% of the original size.
Potential reduce by 19.3 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. OZAS images are well optimized though.
Potential reduce by 350 B
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.
Number of requests can be reduced by 28 (58%)
48
20
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OZAS. 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 6 to 1 for CSS and as a result speed up the page load time.
ozas.lt
724 ms
js
74 ms
mapplic.css
174 ms
mapplic-fix.css
254 ms
style.css
374 ms
fontawesome.css
468 ms
jquery.min.js
467 ms
jquery.mousewheel.js
360 ms
csvparser.js
386 ms
mapplic.js
392 ms
5ee2137384ff8ff8.css
532 ms
1bf74a58515d31fb.css
456 ms
polyfills-5cd94c89d3acac5f.js
600 ms
webpack-018ee347a0a5acf4.js
474 ms
framework-f9ba70b1d8cb0858.js
672 ms
main-efe7db3f831b7a6d.js
602 ms
_app-972ae41c2daccd95.js
824 ms
962-c6ceba4a7822b19f.js
601 ms
240-362dd2b22aacdcec.js
711 ms
198-1765f6694f5a53c4.js
723 ms
index-e19ba8f7ff99ea9b.js
711 ms
_buildManifest.js
710 ms
_ssgManifest.js
765 ms
_middlewareManifest.js
759 ms
kart_d273b103f9.svg
733 ms
food_restaurant_icon_6282eeb1a1.svg
789 ms
supermarket_6a9d7822dc.svg
755 ms
parking_a12a47bd95.svg
766 ms
ozas_plain_4179736b55.png
946 ms
ezgif_com_crop_3_991bbb084e.gif
786 ms
ezgif_com_crop_4_7528fc2f55.gif
848 ms
arrow_down.png
567 ms
Ozas_pavasaris_1920x800_1_ce08e5b5f9.jpg
1326 ms
car_1044_4cf56c1adf.svg
734 ms
Vector_faf861564f.svg
704 ms
maps_location_11100_43bf180107.svg
691 ms
naujienlaiskio_2506x792_86bf6fa883.jpg
910 ms
Vector_b0656786fd.png
786 ms
instagram_icon_c25e77a4aa.png
799 ms
Subtract_1abe2bb818.png
821 ms
apple_f9d32ec5b4.png
857 ms
google_ecf2366703.png
885 ms
nepirockcastle_logo_673a6d86c4.png
885 ms
widget.js
169 ms
Vector.2e8fac3e.png
201 ms
Vector2.546f02b5.png
242 ms
widget_app_base_1715342638247.js
190 ms
hRgSfktzxw
335 ms
lt.json
9 ms
ozas.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
ozas.lt 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
ozas.lt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Ozas.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 Ozas.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.
ozas.lt
Open Graph data is detected on the main page of OZAS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: