Mapy.cz - SEO Checker - Website Review

Your Website Score is

Similar Ranking

ФЕДЕРАЛЬНАЯ НАЛОГОВАЯ СЛУЖБА

nalog.ru

L'EXPRESS - ACTUALITÉS POLITIQUE, MONDE, ECONOMIE ET CULTURE - L'EXPRESS

lexpress.fr

ENTREPRENEUR - START, RUN AND GROW YOUR BUSINESS.

entrepreneur.com

THE DAILY BEAST

thedailybeast.com

SKY SPORTS - SPORTS NEWS, TRANSFERS, SCORES | WATCH LIVE SPORT

skysports.com

HOWSTUFFWORKS - LEARN HOW EVERYTHING WORKS!

howstuffworks.com

HOME | GLOBAL | SIEMENS

siemens.com

Latest Sites

GOLIKE

tiktok.golike.one

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

JOBIFY

jobify2u.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

90 mapy.cz Last Updated: 1 year

Success 47% of passed verification steps

Warning 38% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 57%

Best Practices Desktop Score 62%

SEO Desktop Score 90%

Progressive Web App Desktop Score 23%

Performance Mobile Score 12%

Best Practices Mobile Score 54%

SEO Mobile Score 92%

Progressive Web App Mobile Score 26%

Page Authority Authority 67%

Domain Authority Domain Authority 92%

Moz Rank 6.7/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 7 Characters

MAPY.CZ

Meta Description 327 Characters

Nejpoužívanější mapový portál v ČR s celou řadou tématických map - základní, turistickou, cyklistickou, dopravní a plno dalších. Nabízí možnost reálného leteckého, panoramatického nebo 3D pohledu. Rozsáhlé množství obsahu, firem a turistických bodů zájmu. Umožňuje vyhledávání, plánování tras, měření a tvorbu vlastních značek.

Effective URL 14 Characters

http://mapy.cz

Meta Keywords 4 Detected

Mapy mapy online mapa ČR hrady a zámky mapa

Google Preview Your look like this in google search result

MAPY.CZ

http://mapy.cz

Nejpoužívanější mapový portál v ČR s celou řadou tématických map - základní, turistickou, cyklistickou, dopravní a plno dalších. Nabízí možnost reálné

Robots.txt File Detected

http://mapy.cz/robots.txt

Sitemap.xml File Detected

http://mapy.cz/sitemap.xml

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

Updated: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 621 months 25 days

REG-IGNUM REG-IGNUM REG-MOJEID REG-IGNUM REG-IGNUM ,

Registrar Address: Radlická 3294/10 Praha 5 15000 CZ Radlická 3294/10 Praha 5 150 00 CZ ,

Seznam.cz, a.s. Vlastimil Pečínka

Nameservers

ans.seznam.cz

(77.75.74.80,

2a02:598:3333::3)

ams.seznam.cz

(77.75.75.230,

2a02:598:4444::4)

Page Size Code & Text Ratio

Document Size: ~27.53 KB

Code Size: ~4.52 KB

Text Size: ~23 KB Ratio: 83.57%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Nginx

Web Servers

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Server response times are low (TTFB) Root document took 340 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 620 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 16 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 70 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.5 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Speed Index 2.5 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.3 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 2,073 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.1 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.8 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 13 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoids an excessive DOM size 204 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

First Meaningful Paint 1.9 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 100 requests • 2,073 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 65 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 120 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.5 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 14.4 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 10 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Remove unused CSS Potential savings of 85 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 824 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Avoid multiple page redirects Potential savings of 340 ms

Redirects introduce additional delays before the page can be loaded

Does not use HTTPS 1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Mobile

Page load is not fast enough on mobile networks Interactive at 13.2 s

A fast page load over a cellular network ensures a good mobile user experience

First Contentful Paint (3G) 16362 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 70 ms

Tap targets are sized appropriately 100% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 86.84% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 86 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 537 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Does not use HTTPS 1 insecure request found

Avoid multiple page redirects Potential savings of 1,110 ms

Redirects introduce additional delays before the page can be loaded

Server response times are low (TTFB) Root document took 230 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 2,920 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Minimize third-party usage Third-party code blocked the main thread for 40 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 550 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 2.4 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 5 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 9.1 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 9.6 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 1,693 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 7.7 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 13 chains found

Avoids an excessive DOM size 207 elements

First Meaningful Paint 8.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 93 requests • 1,693 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 57 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 460 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 13.2 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Server: nginx
Date: Mon, 09 Dec 2019 08:21:31 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Keep-Alive: timeout=60
Pragma: 
Set-Cookie: abundance=420f917b924473c131018c730a5f439989e53ba9; Domain=mapy.cz; Max-Age=31536000; Secure; Path=/
Expires: Mon, 09 Dec 2019 08:21:30 GMT
Cache-Control: no-cache
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	mapy.cz	77.75.77.138	IN	250
A	mapy.cz	77.75.79.138	IN	250
NS	mapy.cz	ans.seznam.cz	IN	333
NS	mapy.cz	ams.seznam.cz	IN	333
MX	mapy.cz	firma-smtp1.seznam.cz	IN	300
TXT	mapy.cz	wwrr 77.75.79.138 1 tcp 443 30 6 3	IN	300
TXT	mapy.cz	google-site-verification=FmXf3hm-zm9d3c2zdkRbK_4rHdWUM6H413VbBMQond4	IN	300
TXT	mapy.cz	facebook-domain-verification=6mdnuyz6a3d469ymbwxomlgo643ire	IN	300
TXT	mapy.cz	wwrr 77.75.77.138 1 tcp 443 30 6 3	IN	300
TXT	mapy.cz	wwrr 2a02:598:a::79:138 1 tcp 443 30 6 3	IN	300
TXT	mapy.cz	wwrr 2a02:598:2::1138 1 tcp 443 30 6 3	IN	300
AAAA	mapy.cz	2a02:598:a::79:138	IN	249
AAAA	mapy.cz	2a02:598:2::1138	IN	249

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

90 mapy.cz Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Nginx

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments