3.9 sec in total
300 ms
3.4 sec
208 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 300 ms and then it took 3.6 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
20/100
10%
Value5.0 s
27/100
25%
Value6.9 s
33/100
10%
Value1,680 ms
11/100
30%
Value0.015
100/100
15%
Value13.0 s
12/100
10%
300 ms
380 ms
550 ms
144 ms
239 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 65% of them (65 requests) were addressed to the original Navstevalekara.sk, 8% (8 requests) were made to Static.xx.fbcdn.net and 5% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (695 ms) belongs to the original domain Navstevalekara.sk.
Page size can be reduced by 391.0 kB (44%)
897.6 kB
506.6 kB
In fact, the total size of Navstevalekara.sk main page is 897.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. 65% of websites need less resources to load. Javascripts take 695.8 kB which makes up the majority of the site volume.
Potential reduce by 38.7 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 38.7 kB or 74% of the original size.
Potential reduce by 14.7 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 14.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 332.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 332.8 kB or 48% of the original size.
Potential reduce by 4.8 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 has all CSS files already compressed.
Number of requests can be reduced by 56 (62%)
91
35
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 26 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
navstevalekara.sk
300 ms
www.navstevalekara.sk
380 ms
www.navstevalekara.sk
550 ms
style.css.php
144 ms
mkl.tools.js
239 ms
jquery.js
384 ms
selectize.js
376 ms
jquery.page.js
282 ms
jquery.fancybox.js
284 ms
page.js
292 ms
script.js
332 ms
script.js
375 ms
script.js
379 ms
cookieconsent.min.js
49 ms
adsbygoogle.js
133 ms
js
122 ms
conversion.js
114 ms
css2
35 ms
default.css
247 ms
font-awesome.min.css
287 ms
jquery.fancybox.css
326 ms
jquery.menu.css
325 ms
jquery.ui.css
331 ms
ol.css
332 ms
selectize.css
345 ms
wfmi-style.css
381 ms
style.css
419 ms
style.css
420 ms
style.css
423 ms
style.css
427 ms
style.css
441 ms
style.css
477 ms
style.css
511 ms
style.css
512 ms
style.css
516 ms
style.css
519 ms
style.css
538 ms
style.css
571 ms
style.css
603 ms
menu.css
604 ms
style.css
612 ms
style.css
635 ms
responsive.css
665 ms
selectize.css
695 ms
font-awesome.min.css
161 ms
gtm.js
73 ms
logo-header.png
130 ms
img-header.png
129 ms
9e3a06c82e195e65392f226cd93102500d7c0bcc.jpg
201 ms
2f187d1cdd4b96fbb34f43ccff1be8c0d51bef70.JPG
201 ms
31b278d4b1d37d238274355c9868f1a4da1d46dc.JPG
201 ms
976ed56368205630bb528fe503aac2354db63296.jpg
280 ms
f-95e0fb3ff8aaaa88a402bab140fc12888080549b:uhJcoOtCQec,.jpg
366 ms
f-5f6900ec0b0898fb7e9db10214ea57b8a33d8177:4505KzWKrd4,.png
339 ms
f-280fbac6937d9aa90513687d6684485c33d9eaa3:4HCw-IuMs8c,.JPG
419 ms
f-c3b3aae1a6edb1efb18686bb9c4b862becda86be:bEFEn3fI-jw,.png
540 ms
f-db8d13b296d11d26bceb60ac6b681436054ff224:lII4cCIeO8A,.jpg
575 ms
logo-footer-unb.png
370 ms
logo-footer-unlp.png
388 ms
logo-footer-zvld.png
450 ms
logo-white.png
462 ms
show_ads_impl.js
238 ms
sdk.js
58 ms
sk.svg
390 ms
cz.svg
412 ms
process-bg.jpg
447 ms
process1.png
430 ms
process2.png
458 ms
process3.png
477 ms
point-li.png
506 ms
rubber-doctor-reg-list.png
513 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
114 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
128 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
137 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
137 ms
4UaHrEJCrhhnVA3DgluAx60.ttf
157 ms
108 ms
sdk.js
15 ms
fontawesome-webfont.woff
633 ms
85 ms
zrt_lookup.html
21 ms
print.css
96 ms
light-bottom.css
17 ms
sodar
71 ms
page.php
137 ms
logo.png
12 ms
sodar2.js
18 ms
runner.html
6 ms
aframe
22 ms
wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js
5 ms
BcW4HD-pxEe.css
28 ms
AkV4cevgxL7.js
40 ms
Y4zFOWmUObv.js
73 ms
HbT8HXdZYIC.js
88 ms
Ue-M3hwtZyC.js
123 ms
TwSfsj5nvl7.js
91 ms
p55HfXW__mM.js
38 ms
277679598_351618567008243_8517294510573660304_n.jpg
48 ms
277578504_351618563674910_3982938484999745129_n.jpg
47 ms
UXtr_j2Fwe-.png
26 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
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 data is detected on the main page of Navstevalekara. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: