4.3 sec in total
401 ms
3.6 sec
218 ms
Welcome to navstevalekara.sk homepage info - get ready to check Navstevalekara best content for Slovakia right away, or after learning these important things about navstevalekara.sk
Prehľadný, rozsiahly a spoľahlivý zoznam lekárov, zdravotníckych zariadení, lekární a pohotovostí na Slovensku.
Visit navstevalekara.skWe analyzed Navstevalekara.sk page load time and found that the first response time was 401 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
navstevalekara.sk performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value5.0 s
27/100
25%
Value6.7 s
36/100
10%
Value1,060 ms
25/100
30%
Value0.046
99/100
15%
Value10.3 s
25/100
10%
401 ms
770 ms
25 ms
129 ms
205 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 63% of them (63 requests) were addressed to the original Navstevalekara.sk, 10% (10 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (888 ms) belongs to the original domain Navstevalekara.sk.
Page size can be reduced by 309.8 kB (56%)
550.1 kB
240.3 kB
In fact, the total size of Navstevalekara.sk main page is 550.1 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. 55% of websites need less resources to load. CSS take 189.0 kB which makes up the majority of the site volume.
Potential reduce by 29.8 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 29.8 kB or 75% of the original size.
Potential reduce by 17.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. Obviously, Navstevalekara needs image optimization as it can save up to 17.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 113.8 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 113.8 kB or 60% of the original size.
Potential reduce by 148.9 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. Navstevalekara.sk needs all CSS files to be minified and compressed as it can save up to 148.9 kB or 79% of the original size.
Number of requests can be reduced by 46 (51%)
91
45
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Navstevalekara. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
navstevalekara.sk
401 ms
www.navstevalekara.sk
770 ms
css
25 ms
style.css.php
129 ms
mkl.tools.js
205 ms
jquery.js
314 ms
swfobject.js
212 ms
jquery.page.js
214 ms
jquery.fancybox.js
217 ms
page.js
232 ms
script.js
303 ms
script.js
315 ms
script.js
318 ms
cookieconsent.min.js
8 ms
conversion.js
14 ms
default.css
201 ms
font-awesome.min.css
216 ms
jquery.fancybox.css
279 ms
jquery.menu.css
288 ms
jquery.ui.css
299 ms
style.css
302 ms
style.css
307 ms
style.css
320 ms
style.css
382 ms
style.css
388 ms
style.css
404 ms
style.css
406 ms
style.css
413 ms
style.css
425 ms
style.css
482 ms
style.css
488 ms
style.css
509 ms
style.css
511 ms
menu.css
523 ms
style.css
583 ms
style.css
587 ms
responsive.css
614 ms
font-awesome.min.css
131 ms
ga.js
79 ms
logo-header.png
114 ms
img-header.png
114 ms
9e3a06c82e195e65392f226cd93102500d7c0bcc.jpg
163 ms
5a674e9717a6b8b951b088f0969d4c7bfa3ed056.jpg
163 ms
5824c763e3a1c6206774a9a9034fcb7a7fd89f49.JPG
164 ms
56a0d7656678174f57c68c2514e8eddbd5e1733c.jpg
163 ms
f-4b011cb4cf62166e5cc89b6e64b1bf26e23bdc64:BBiCWLXyBI0,.JPG
282 ms
f-280fbac6937d9aa90513687d6684485c33d9eaa3:4HCw-IuMs8c,.JPG
327 ms
f-92606077634438c43fbaf414fce0efe4d7ca7208:Om5WRy97g2A,.jpg
697 ms
f-4acec8829747cb7903851035bd7320b6a7116a5d:bEFEn3fI-jw,.png
426 ms
f-d3b7c234f0b29275649ca70e27482a390f79cb65:F2nG6sjPDnY,.JPG
484 ms
f-bcf3cd95ccc5a07ba96abff3b8567940143147dc:q77sjoG-ozg,.png
362 ms
f-bb4d7837c0dd6233de8e587a0d00b4e1c7f65197:E4zAGWp52W8,.jpg
630 ms
logo-footer-slk.png
432 ms
logo-footer-unb.png
463 ms
logo-footer-unlp.png
526 ms
logo-footer-aopp.png
538 ms
logo-footer-loz.png
563 ms
sdk.js
111 ms
sk.svg
583 ms
cz.svg
620 ms
process-bg.jpg
638 ms
process1.png
641 ms
process2.png
674 ms
process3.png
703 ms
point-li.png
709 ms
rubber-doctor-reg-list.png
726 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
51 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
52 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
85 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
81 ms
0daoUMW28nkWOnFz2G4AAi3USBnSvpkopQaUR-2r7iU.ttf
86 ms
90 ms
fontawesome-webfont.woff
888 ms
__utm.gif
39 ms
58 ms
117 ms
xd_arbiter.php
85 ms
xd_arbiter.php
130 ms
print.css
109 ms
light-bottom.css
22 ms
logo.png
3 ms
page.php
99 ms
q8sTdrz2ueE.css
89 ms
_rx8naC75Dy.js
144 ms
t-KLv3gqZy0.js
142 ms
yWVU4L-lSZ6.js
187 ms
12115524_965748743507211_6098211339035427484_n.jpg
91 ms
12115519_965744853507600_3891877403831026481_n.jpg
68 ms
226867_215349651816623_4283273_n.jpg
75 ms
200297_1787238968256_8093141_n.jpg
101 ms
30225_127143073965169_7306967_n.jpg
82 ms
11921885_901619286554551_8120385010917152787_n.jpg
85 ms
11261700_10204095606486140_7380562211617165025_n.jpg
152 ms
11988593_10206424997857244_6316544991870770078_n.jpg
88 ms
wL6VQj7Ab77.png
20 ms
CSXXCvknpgK.png
19 ms
R9a_DtVRZgv.js
21 ms
cUDgRFxaoIk.js
20 ms
0JBr1QHp8Gi.js
21 ms
kDOzhTr2W91.js
38 ms
navstevalekara.sk accessibility score
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
Links do not have a discernible name
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.
navstevalekara.sk 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
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
navstevalekara.sk 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
SK
SK
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Navstevalekara.sk can be misinterpreted by Google and other search engines. Our service has detected that Slovak is used on the page, and it matches the claimed language. Our system also found out that Navstevalekara.sk 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.
navstevalekara.sk
Open Graph description is not detected on the main page of Navstevalekara. 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: