4.3 sec in total
342 ms
3.9 sec
109 ms
Visit letovi.hr now to see the best up-to-date Letovi content for Croatia and also check out these interesting facts you probably never knew about letovi.hr
Kupi najpovoljniju avio kartu prema željenoj destinaciji u nekoliko jednostavnih koraka uz mogućnost obročnog plaćanja do 12 rata. Letovi.hr.
Visit letovi.hrWe analyzed Letovi.hr page load time and found that the first response time was 342 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
letovi.hr performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value9.3 s
1/100
25%
Value7.3 s
28/100
10%
Value570 ms
52/100
30%
Value0.012
100/100
15%
Value10.5 s
23/100
10%
342 ms
455 ms
771 ms
699 ms
586 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Letovi.hr, 83% (79 requests) were made to Etours.hr and 4% (4 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Etours.hr.
Page size can be reduced by 189.2 kB (19%)
1.0 MB
811.6 kB
In fact, the total size of Letovi.hr main page is 1.0 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. 60% of websites need less resources to load. Javascripts take 614.7 kB which makes up the majority of the site volume.
Potential reduce by 55.5 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 14.2 kB, which is 22% 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 55.5 kB or 85% of the original size.
Potential reduce by 18.1 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. Letovi images are well optimized though.
Potential reduce by 110.4 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 110.4 kB or 18% of the original size.
Potential reduce by 5.2 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. Letovi.hr has all CSS files already compressed.
Number of requests can be reduced by 68 (81%)
84
16
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Letovi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
letovi.hr
342 ms
letovi.hr
455 ms
www.letovi.hr
771 ms
bootstrap.min.css
699 ms
royalslider.css
586 ms
slick.css
589 ms
slick-theme.css
597 ms
jquery-ui.css
600 ms
jquery-ui.theme.css
608 ms
eselect.styles.min.css
695 ms
swipebox.min.css
704 ms
datatables.css
709 ms
jquery.mCustomScrollbar.min.css
711 ms
styles.css
847 ms
styles2.css
806 ms
jquery.min.js
922 ms
js
69 ms
api.js
50 ms
bootstrap.min.js
813 ms
jquery.royalslider.min.js
932 ms
jquery.swipebox.min.js
818 ms
jquery.validate.1.12.0.min.js
915 ms
slick.min.js
925 ms
stickykit.min.js
927 ms
jquery.mCustomScrollbar.concat.min.js
963 ms
jquery.eselect.js
1024 ms
jquery-ui.js
1054 ms
jquery.ui.touch-punch.js
1035 ms
datepicker-hr.js
1036 ms
moment.min.js
1174 ms
imageMapResizer.min.js
1075 ms
jquery.viewportchecker.min.js
1133 ms
numeral.min.js
1145 ms
locales.min.js
1146 ms
cleave.min.js
1162 ms
enquire.min.js
1187 ms
sticky-kit.js
1242 ms
datatables-langs.js
1253 ms
datatables.js
1671 ms
rotator.js
1270 ms
gallery.js
1284 ms
slick-theme-list.js
720 ms
slick-trips-list.js
769 ms
autocomplete.js
771 ms
tabs.js
783 ms
reservation-form.js
794 ms
elatus-number.js
723 ms
aside-search-form.js
764 ms
voucher.js
773 ms
services-list.js
780 ms
rotator-small.js
799 ms
aside-search-form-destinations.js
724 ms
slick-top-offers-hotels.js
762 ms
lightbox.js
768 ms
fonts.css
745 ms
hotel-search.js
760 ms
hotel-reservation.js
753 ms
trip-reservation.js
821 ms
rentacar.js
826 ms
functions.js
821 ms
functions_aviokarte.js
790 ms
letovi_logo.svg
126 ms
icon_plane_orange.svg
177 ms
icon_line.svg
266 ms
icon_calendar.svg
274 ms
icon_person.svg
272 ms
icon_minus.svg
273 ms
icon_plus.svg
269 ms
icon_arrow_down_orange.svg
274 ms
icon_true.svg
339 ms
lot-polish-airlines-2.jpg
446 ms
avio-2_161eae0c10f56f.jpg
449 ms
credit-card-3.jpg
451 ms
logo_letovi.svg
345 ms
earth.gif
582 ms
recaptcha__en.js
133 ms
js
70 ms
analytics.js
205 ms
raleway-regular-webfont.woff
445 ms
raleway-medium-webfont.woff
394 ms
raleway-light-webfont.woff
493 ms
raleway-bold-webfont.woff
502 ms
raleway-black-webfont.woff
503 ms
ajax-loader.gif
315 ms
icon_calendar_prev.svg
351 ms
ui-icons_ffffff_256x240.png
406 ms
icon_calendar_next.svg
406 ms
anchor
28 ms
collect
13 ms
styles__ltr.css
4 ms
recaptcha__en.js
14 ms
logo_48.png
15 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
18 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
21 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
24 ms
letovi.hr accessibility score
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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Form elements do not have associated labels
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.
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.
letovi.hr 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
Page has valid source maps
letovi.hr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
HR
HR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Letovi.hr can be misinterpreted by Google and other search engines. Our service has detected that Croatian is used on the page, and it matches the claimed language. Our system also found out that Letovi.hr 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.
letovi.hr
Open Graph description is not detected on the main page of Letovi. 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: