PROLEKARE.CZ Největší informační zdroj pro lékaře - proLékaře.cz


prolekare.cz website information.

prolekare.cz domain name is registered by .CZ top-level domain registry. See the other sites registred in .CZ domain zone.

No name server records were found.

and probably website prolekare.cz is hosted by Hetzner Online GmbH web hosting company. Check the complete list of other most popular websites hosted by Hetzner Online GmbH hosting company.

According to Alexa traffic rank the highest website prolekare.cz position was 20724 (in the world). The lowest Alexa rank position was 999709. Now website prolekare.cz ranked in Alexa database as number 373016 (in the world).

Website prolekare.cz Desktop speed measurement score (72/100) is better than the results of 54.39% of other sites shows that the page desktop performance can be improved.

prolekare.cz Mobile usability score (87/100) is better than the results of 28.3% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of prolekare.cz (50/100) is better than the results of 33.92% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Sep-23-2024 N/AN/A
Sep-22-2024 373,016-1,147
Sep-21-2024 371,8694,913
Sep-20-2024 376,782-5,572
Sep-19-2024 371,210-2,903
Sep-18-2024 368,3073,279
Sep-17-2024 371,586-9,328

Advertisement

prolekare.cz Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



prolekare.cz whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


prolekare.cz server information

Servers Location

IP Address
Country
Region
City

prolekare.cz desktop page speed rank

Last tested: 2015-09-10


Desktop Speed Medium
72/100

prolekare.cz Desktop Speed Test Quick Summary


priority - 18 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 12 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://media.meditorial.cz/jscript/jquery.min.!min.js?t=1425455318
http://media.meditorial.cz/jscript/jquery.i18n.!min.js?t=1438863995
http://media.meditorial.cz/jscript/jquery-ui.min.!min.js?t=1420547492
http://media.meditorial.cz/jscript/md.!min.js?t=1438864164
http://media.meditorial.cz/jscript/swfobject.!min.js?t=1420547492
http://www.prolekare.cz/jscript/main.!min.js?t=1441795911
http://www.prolekare.cz/jscript/mediclub.!min.js?t=1418207301
http://www.prolekare.cz/jscript/event.!min.js?t=1417508936
http://www.prolekare.cz/jscript/re_script.!min.js?t=1426587246
http://www.prolekare.cz/jscript/jquery.slider.min.!min.js?t=1417508936
http://gacz.hit.gemius.pl/xgemius.js
http://ads.meditorial.cz/www/delivery/ajs.php?zone…%3A//www.prolekare.cz/

Optimize CSS Delivery of the following:

http://media.meditorial.cz/css/gallery.!min.css?t=1417077732
http://media.meditorial.cz/css/jquery-ui.!min.css?t=1415891616
http://www.prolekare.cz/css/redesign/main.!min.css?t=1441795911
http://www.prolekare.cz/css/main-barvy.css

priority - 11 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 107.8KiB (81% reduction).

Compressing and resizing http://www.prolekare.cz/dbpic/smclogo could save 50.2KiB (85% reduction).
Compressing and resizing http://www.prolekare.cz/dbpic/logo_pubmed could save 24.1KiB (94% reduction).
Compressing and resizing http://www.prolekare.cz/dbpic/logo_CLS_cerne could save 21.9KiB (85% reduction).
Compressing and resizing http://www.prolekare.cz/dbpic/MSF_logo could save 8.7KiB (68% reduction).
Losslessly compressing http://www.prolekare.cz/img/user-bar.png could save 1.2KiB (28% reduction).
Losslessly compressing http://www.prolekare.cz/img/print-header.gif could save 976B (27% reduction).
Losslessly compressing http://www.prolekare.cz/img/user-bar-logout.png could save 875B (85% reduction).

priority - 5 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.googletagservices.com/tag/js/gpt.js (60 minutes)
http://stats.g.doubleclick.net/dc.js (2 hours)
http://www.prolekare.cz/dbpic/MSF_logo (2 hours)
http://www.prolekare.cz/dbpic/jp_52365_p_1-f65_65 (2 hours)
http://www.prolekare.cz/dbpic/jp_52732_p_1-f65_65 (2 hours)
http://www.prolekare.cz/dbpic/jp_52866_t_1-f65_65 (2 hours)
http://www.prolekare.cz/dbpic/logo_CLS_cerne (2 hours)
http://www.prolekare.cz/dbpic/logo_pubmed (2 hours)
http://www.prolekare.cz/dbpic/smclogo (2 hours)

priority - 4 Reduce server response time

In our test, your server responded in 0.61 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 0 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 2.4KiB (16% reduction).

Minifying http://www.prolekare.cz/ could save 2.4KiB (16% reduction) after compression.

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 632B (13% reduction).

Minifying http://gacz.hit.gemius.pl/xgemius.js could save 632B (13% reduction) after compression.

prolekare.cz Desktop Resources

Total Resources50
Number of Hosts17
Static Resources33
JavaScript Resources21
CSS Resources4

prolekare.cz Desktop Resource Breakdown

prolekare.cz mobile page speed rank

Last tested: 2019-06-22


Mobile Speed Bad
50/100

prolekare.cz Mobile Speed Test Quick Summary


priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:

https://pl.mdcdn.cz/bundles/prolekare/css/main-PL.css?version=1560838681
https://fonts.googleapis.com/css?family=PT+Serif:400,700&subset=latin-ext
https://fonts.googleapis.com/css?family=Roboto:400,500&subset=latin-ext

priority - 34 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://prolekare.cz/
https://prolekare.cz/
https://www.prolekare.cz/

priority - 16 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 156.2KiB (50% reduction).

Compressing https://pl.mdcdn.cz/media/image/67b660a13f8a7267c8…png?version=1532939735 could save 107.1KiB (71% reduction).
Compressing https://pl.mdcdn.cz/media/image/9e13a544daad0ca1cc…peg?version=1531214219 could save 13.5KiB (67% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…e7e1c1fb0e071bec0.jpeg could save 3.7KiB (31% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…69658b09ddf50fd48.jpeg could save 2.6KiB (37% reduction).
Compressing https://pl.mdcdn.cz/media/cache/journal_issue/medi…9e8a3bd40b2a0ac1a.jpeg could save 2.5KiB (34% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…666359f51878657a3.jpeg could save 2.4KiB (33% reduction).
Compressing https://pl.mdcdn.cz/media/cache/journal_issue/medi…3c652ef0292cd3e3a.jpeg could save 2.3KiB (36% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…51ce016a504b0f284.jpeg could save 2KiB (31% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…af6374d683a39ba62.jpeg could save 2KiB (31% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…b7eecf68ad6e82da1.jpeg could save 1.9KiB (31% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…c6505b79d6e198ffd.jpeg could save 1.9KiB (40% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…dadf41d8b8041f07a.jpeg could save 1.8KiB (30% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…948bcba0647eb5c68.jpeg could save 1.8KiB (29% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…3b303cb040fc4f0e8.jpeg could save 1.6KiB (33% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…38bde89e03aa976c5.jpeg could save 1.4KiB (29% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…0d4c75fc87dda1905.jpeg could save 1.2KiB (23% reduction).
Compressing https://pl.mdcdn.cz/media/cache/partner_footer/med…5b325a55ce823b760.jpeg could save 945B (11% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…084c16e2a97053c22.jpeg could save 919B (12% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…1a4ba506bde73ab1e.jpeg could save 893B (26% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…4c37634185d646245.jpeg could save 834B (13% reduction).
Compressing https://pl.mdcdn.cz/media/cache/partner_footer/med…26593541f1f3d265f.jpeg could save 780B (13% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…d36fd59d184d1b909.jpeg could save 713B (13% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…5c4feb52468468b65.jpeg could save 709B (12% reduction).
Compressing https://pl.mdcdn.cz/media/cache/article_list_item_…d1e9b96fea43adf24.jpeg could save 664B (12% reduction).

priority - 11 Reduce server response time

In our test, your server responded in 0.95 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 8 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://www.prolekare.cz/bundles/fenix/js/i18n.js (expiration not specified)
https://www.prolekare.cz/bundles/fenix/js/lib/i18n.min.js (expiration not specified)
https://www.prolekare.cz/bundles/prolekare/bower/j…ization/messages_cs.js (expiration not specified)
https://www.googletagmanager.com/gtm.js?id=GTM-M7DD5MN (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/262275…7586?v=2.8.51&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 (20 minutes)
https://i.ytimg.com/vi/No0UsHp2N9w/hqdefault.jpg (2 hours)
https://ssl.google-analytics.com/ga.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.4KiB (19% reduction).

Minifying https://spir.hit.gemius.pl/xgemius.js could save 808B (12% reduction) after compression.
Minifying https://connect.facebook.net/signals/plugins/inferredEvents.js?v=2.8.51 could save 646B (85% reduction) after compression.

prolekare.cz Mobile Resources

Total Resources77
Number of Hosts20
Static Resources59
JavaScript Resources23
CSS Resources6

prolekare.cz Mobile Resource Breakdown

prolekare.cz mobile page usability

Last tested: 2019-06-22


Mobile Usability Good
87/100

prolekare.cz Mobile Usability Test Quick Summary


priority - 13 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/kreditovane-k…e-bezpecne-180" class="m-list-column__link">Fluoridy - stále bezpečné?</a> and 225 others are close to other tap targets.
The tap target <a href="/kontakt" class="m-nav-base__li…nav-base__link">Kontakt</a> and 1 others are close to other tap targets.

prolekare.cz similar domains

Similar domains:
www.prolekare.com
www.prolekare.net
www.prolekare.org
www.prolekare.info
www.prolekare.biz
www.prolekare.us
www.prolekare.mobi
www.rolekare.cz
www.prolekare.cz
www.orolekare.cz
www.porolekare.cz
www.oprolekare.cz
www.lrolekare.cz
www.plrolekare.cz
www.lprolekare.cz
www.polekare.cz
www.peolekare.cz
www.preolekare.cz
www.perolekare.cz
www.pdolekare.cz
www.prdolekare.cz
www.pdrolekare.cz
www.pfolekare.cz
www.prfolekare.cz
www.pfrolekare.cz
www.ptolekare.cz
www.prtolekare.cz
www.ptrolekare.cz
www.prlekare.cz
www.prilekare.cz
www.proilekare.cz
www.priolekare.cz
www.prklekare.cz
www.proklekare.cz
www.prkolekare.cz
www.prllekare.cz
www.prollekare.cz
www.prlolekare.cz
www.prplekare.cz
www.proplekare.cz
www.prpolekare.cz
www.proekare.cz
www.propekare.cz
www.prolpekare.cz
www.prooekare.cz
www.proloekare.cz
www.proolekare.cz
www.prokekare.cz
www.prolkekare.cz
www.prolkare.cz
www.prolwkare.cz
www.prolewkare.cz
www.prolwekare.cz
www.prolskare.cz
www.proleskare.cz
www.prolsekare.cz
www.proldkare.cz
www.proledkare.cz
www.proldekare.cz
www.prolrkare.cz
www.prolerkare.cz
www.prolrekare.cz
www.proleare.cz
www.prolejare.cz
www.prolekjare.cz
www.prolejkare.cz
www.proleiare.cz
www.prolekiare.cz
www.proleikare.cz
www.prolemare.cz
www.prolekmare.cz
www.prolemkare.cz
www.prolelare.cz
www.proleklare.cz
www.prolelkare.cz
www.proleoare.cz
www.prolekoare.cz
www.proleokare.cz
www.prolekre.cz
www.prolekqre.cz
www.prolekaqre.cz
www.prolekqare.cz
www.prolekwre.cz
www.prolekawre.cz
www.prolekware.cz
www.proleksre.cz
www.prolekasre.cz
www.proleksare.cz
www.prolekzre.cz
www.prolekazre.cz
www.prolekzare.cz
www.prolekae.cz
www.prolekaee.cz
www.prolekaree.cz
www.prolekaere.cz
www.prolekade.cz
www.prolekarde.cz
www.prolekadre.cz
www.prolekafe.cz
www.prolekarfe.cz
www.prolekafre.cz
www.prolekate.cz
www.prolekarte.cz
www.prolekatre.cz
www.prolekar.cz
www.prolekarw.cz
www.prolekarew.cz
www.prolekarwe.cz
www.prolekars.cz
www.prolekares.cz
www.prolekarse.cz
www.prolekard.cz
www.prolekared.cz
www.prolekarr.cz
www.prolekarer.cz
www.prolekarre.cz

prolekare.cz Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


prolekare.cz TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.