Stranamam.ru - SEO Checker

Your Website Score is

Similar Ranking

WEBSITE VALUE CALCULATOR AND WEB INFORMATION

websiteoutlook.com

INTERNET SPEED TEST | FAST.COM

fast.com

ERROR PAGE | EBAY

ebay.ie

THE WORK MANAGEMENT PLATFORM | PIPEFY

pipefy.com

MIS MARCADORES: RESULTADOS DE FÚTBOL EN DIRECTO, FÚTBOL EN VIVO

mismarcadores.com

企查查-企业工商信息查询系统_查企业_查老板_查关系就上企查查!

qichacha.com

URLAUB: BIS 40% RABATT BEIM MARKTFÜHRER | AB-IN-DEN-URLAUB.DE

ab-in-den-urlaub.de

Latest Sites

PORTSTONE PARTNERS LIMITED

portstonepartnersltd.com

VENICTRADE.COM

venictrade.com

COINLUNO.COM

coinluno.com

SIGNCURRENCY.COM

signcurrency.com

ALLTRADESFX.COM

alltradesfx.com

MODERN KITCHENS | READIKIT | HOME PAGE

readikit.com

av4.xyz

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

47 stranamam.ru Last Updated: 10 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 61%

Best Practices Desktop Score 54%

SEO Desktop Score 90%

Progressive Web App Desktop Score 23%

Performance Mobile Score 28%

Best Practices Mobile Score 54%

SEO Mobile Score 91%

Progressive Web App Mobile Score 26%

Page Authority Authority 48%

Domain Authority Domain Authority 65%

Moz Rank 4.8/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 23 Characters

- : , , , , ,

Meta Description 0 Characters

NO DATA

Effective URL 23 Characters

http://www.stranamam.ru

Google Preview Your look like this in google search result

- : , , , , ,

http://www.stranamam.ru

Robots.txt File Detected

http://stranamam.ru/robots.txt

Sitemap.xml File Detected

http://stranamam.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: 2009-09-13 / 11 years

Expires on: 2020-09-13 / 1 months 11 days

DOMENUS-RU ,

Nameservers

ns10.hoster.ru.

ns11.hoster.ru.

Page Size Code & Text Ratio

Document Size: ~267 B

Code Size: ~253 B

Text Size: ~14 B Ratio: 5.24%

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

First Meaningful Paint 1.2 s

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

Keep request counts low and transfer sizes small 259 requests • 2,731 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 126 resources found

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

Max Potential First Input Delay 90 ms

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

Time to Interactive 4.8 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 20.3 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 561 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 346 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 190 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

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

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

Eliminate render-blocking resources Potential savings of 730 ms

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

Efficiently encode images Potential savings of 38 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 126 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 20 ms

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

JavaScript execution time 0.3 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 582 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

Properly size images Potential savings of 260 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.3 s

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

First CPU Idle 2.8 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,556 KB

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

Minimizes main-thread work 1.3 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

Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

Avoid an excessive DOM size 1,546 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)

Minify JavaScript Potential savings of 161 KB

Minifying JavaScript files can reduce payload sizes and script parse time

Mobile

Total Blocking Time 350 ms

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

JavaScript execution time 1.2 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 790 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

Properly size images Potential savings of 2 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 5.9 s

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

First CPU Idle 11.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 2,538 KB

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

Minimize main-thread work 3.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 3.9 s

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

Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 16 chains found

Avoid an excessive DOM size 1,450 elements

Minify JavaScript Potential savings of 161 KB

Minifying JavaScript files can reduce payload sizes and script parse time

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 249 requests • 2,538 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 118 resources found

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

Max Potential First Input Delay 260 ms

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

Time to Interactive 19.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

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

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

Estimated Input Latency 10 ms

First Contentful Paint (3G) 8168.5 ms

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

Tap targets are not sized appropriately 98% 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.49% 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 561 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 307 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 630 ms

Redirects introduce additional delays before the page can be loaded

Does not use HTTPS 1 insecure request found

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,280 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 126 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 200 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

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, 07 Jan 2020 16:30:06 GMT
Content-Type: text/html; charset=windows-1251
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/5.5.30
Expires: Tue, 07 Jan 2020 16:30:06 GMT
Last-Modified: Tue, 07 Jan 2020 16:30:06 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: rc=1; expires=Wed, 06-Jan-2021 16:30:06 GMT; Max-Age=31536000; path=/; domain=.stranamam.ru
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	stranamam.ru	136.243.78.166	IN	1799
NS	stranamam.ru	ns10.hoster.ru	IN	1800
NS	stranamam.ru	ns11.hoster.ru	IN	1800
MX	stranamam.ru	mailx.hoster.ru	IN	1800
TXT	stranamam.ru	v=spf1 include:_spf.hoster.ru +ip4:217.65.3.118/32 +a:stranamam.ru -all	IN	1800

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

47 stranamam.ru Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

comScore

Google Font API

Liveinternet

Nginx

PHP

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