Pochta.ru - SEO Checker - Website Review

Your Website Score is

Similar Ranking

ONLINE KHABAR – NO 1 NEWS PORTAL FROM NEPAL IN NEPALI.

onlinekhabar.com

ANZ PERSONAL BANKING | ACCOUNTS, CREDIT CARDS, LOANS, INSURANCE | ANZ

anz.com

HOME | S.TO - SERIEN ONLINE ANSEHEN & STREAMEN

s.to

NETNAIJA: LATEST MUSIC, VIDEOS, COMEDY, GIST AND MORE

thenetnaija.com

TVCINE E SÉRIES

tvcine.pt

DOWNLOADHELPER - VIDEO DOWNLOAD BROWSER EXTENSION

downloadhelper.net

ЭЛЕКТРОННАЯ БИБЛИОТЕКА RULIT - ЭЛЕКТРОННЫЕ КНИГИ СКАЧАТЬ БЕСПЛАТНО БЕЗ РЕГИСТРАЦИИ. ЧИТАТЬ КНИГИ ОНЛАЙН БЕСПЛАТНО. РУССКАЯ ЛИТЕРАТУРА.

rulit.me

Latest Sites

ELITECOIN INVESTMENT

elitecoinvest.com

EMPIRE-INVESTMENT.COM

empire-investment.com

NEXFAR TRADES | INVESTMENT MADE EASY

nexfartrades.net

digirms.com

TECHCROZ.COM - HOME BASED ONLINE DATA ENTRY WORK IN INDIA

techcroz.com

CAPITAL-FINANCE.US

capital-finance.us

GLOBE MINERSPRO - CRYPTO CURRENCY MINING

globeminerspro.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

42 pochta.ru Last Updated: 1 year

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 67%

Best Practices Desktop Score 92%

SEO Desktop Score 100%

Progressive Web App Desktop Score 31%

Performance Mobile Score 20%

Best Practices Mobile Score 92%

SEO Mobile Score 98%

Progressive Web App Mobile Score 33%

Page Authority Authority 60%

Domain Authority Domain Authority 85%

Moz Rank 6.0/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 12 Characters

ПОЧТА РОССИИ

Meta Description 208 Characters

Тарифы на почтовые отправления. Сведения о системе почтовых переводов, информация об отделениях. Онлайн-заполнение необходимых почтовых бланков, отслеживание почтовых отправлений. Контакты почтовых отделений.

Effective URL 21 Characters

https://www.pochta.ru

Excerpt Page content

Почта России 2019 © АО Почта России Раскрытие информации Пресс-центр О компании

Keywords Cloud Density

почта1 россии1 раскрытие1 информации1 пресс1 центр1 компании1

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
почта	1
россии	1
раскрытие	1
информации	1
пресс	1
центр	1
компании	1

Google Preview Your look like this in google search result

ПОЧТА РОССИИ

https://www.pochta.ru

Тарифы на почтовые отправления. Сведения о системе почтовых переводов, информация об отделениях. Онлайн-заполнение необходимых почтовых бланков, отсле

Robots.txt File Detected

http://pochta.ru/robots.txt

Sitemap.xml File Detected

http://pochta.ru/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: 2001-11-05 / 19 years

Expires on: 2019-11-06 / 17 months 21 days

RU-CENTER-RU ,

Nameservers

dc-ns1.russianpost.ru.

ns2.russianpost.ru.

Page Size Code & Text Ratio

Document Size: ~43.3 KB

Code Size: ~6.14 KB

Text Size: ~37.16 KB Ratio: 85.83%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

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

Desktop

Reduce server response times (TTFB) Root document took 910 ms

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

Eliminate render-blocking resources Potential savings of 450 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 4 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 10 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 600 ms

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

Reduce JavaScript execution time 1.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

Speed Index 3.8 s

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

First CPU Idle 2.4 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,224 KB

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

Minimizes main-thread work 1.9 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.1 s

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

Avoid chaining critical requests 7 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 339 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)

Preload key requests Potential savings of 1,510 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

First Meaningful Paint 1.1 s

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

Keep request counts low and transfer sizes small 42 requests • 1,224 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 7 resources found

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

Max Potential First Input Delay 410 ms

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

Time to Interactive 2.6 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 11.6 s

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

Estimated Input Latency 70 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

Minify CSS Potential savings of 4 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 103 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

Mobile

Time to Interactive 11.4 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 at 11.4 s

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

Estimated Input Latency 1,080 ms

First Contentful Paint (3G) 9336 ms

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

Minify CSS Potential savings of 4 KB

Minifying CSS files can reduce network payload sizes

Tap targets are not sized appropriately 80% 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 95.98% 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 103 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 8 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

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

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

Eliminate render-blocking resources Potential savings of 2,770 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 4 KB

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

Reduce the impact of third-party code Third-party code blocked the main thread for 710 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 4,010 ms

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

Reduce JavaScript execution time 6.9 s

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

Defer offscreen images Potential savings of 9 KB

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

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 9.8 s

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

First CPU Idle 10.7 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,185 KB

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

Minimize main-thread work 8.7 s

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

First Contentful Paint 4.7 s

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

Avoid chaining critical requests 6 chains found

Avoids an excessive DOM size 349 elements

Preload key requests Potential savings of 7,980 ms

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load

First Meaningful Paint 4.7 s

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

Keep request counts low and transfer sizes small 40 requests • 1,185 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 7 resources found

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

Max Potential First Input Delay 1,840 ms

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

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: Tue, 26 Nov 2019 20:02:15 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 0
Connection: keep-alive
X-Content-Type-Options: nosniff
X-XSS-Protection: 1
Set-Cookie: JSESSIONID=EC7B39CE55C12315B3AEFBE7979E4CF9; Path=/; Secure; HttpOnly
Set-Cookie: ANALYTICS_UUID=01fe84ff-cd68-4433-9ae8-a026aae7371c; Domain=.pochta.ru; Expires=Sat, 10-Jul-2066 22:44:23 GMT; Path=/; Secure; HttpOnly
Set-Cookie: GUEST_LANGUAGE_ID=ru_RU; Expires=Sat, 10-Jul-2066 22:44:23 GMT; Path=/; Secure; HttpOnly
Set-Cookie: COOKIE_SUPPORT=true; Expires=Sat, 10-Jul-2066 22:44:23 GMT; Path=/; Secure; HttpOnly
X-UA-Compatible: IE=Edge
Strict-Transport-Security: max-age=31536000; includeSubDomains

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	pochta.ru	91.215.38.80	IN	250
A	pochta.ru	91.215.38.83	IN	250
A	pochta.ru	91.215.37.237	IN	250
A	pochta.ru	91.215.37.236	IN	250
A	pochta.ru	91.215.38.82	IN	250
A	pochta.ru	91.215.37.238	IN	250
A	pochta.ru	91.215.37.235	IN	250
A	pochta.ru	91.215.38.81	IN	250
NS	pochta.ru	ns2.russianpost.ru	IN	299
NS	pochta.ru	dc-ns1.russianpost.ru	IN	299
MX	pochta.ru	d01smtpmm.russianpost.ru	IN	299
MX	pochta.ru	r00smtpmm.russianpost.ru	IN	299
TXT	pochta.ru	mailru-verification: 0112fe2cf35d5a07	IN	299
TXT	pochta.ru	mailru-verification: 5672271d39a20361	IN	299
TXT	pochta.ru	google-site-verification=BtRerE1m3T6h3cj9AW3_c-HhyXKa8smOXAYp2EyxPZ0	IN	299
TXT	pochta.ru	v=spf1 mx -all	IN	299

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

42 pochta.ru Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Google Tag Manager

Java

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