Komus.ru - SEO Checker - Website Review

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

THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ

noithatmanhhe.vn

SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP

nhacanhothongminh.com

CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM

crypto-mining.biz

99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING

999dice.com

RELANDICE BOT FOR 999DICE

relandice.com

❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !

baophong.vn

ONE MORE STEP

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

47 komus.ru Last Updated: 8 months

Success 70% of passed verification steps

Warning 15% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 62%

Best Practices Desktop Score 69%

SEO Desktop Score 90%

Progressive Web App Desktop Score 27%

Performance Mobile Score 21%

Best Practices Mobile Score 69%

SEO Mobile Score 92%

Progressive Web App Mobile Score 33%

Page Authority Authority 49%

Domain Authority Domain Authority 55%

Moz Rank 4.9/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 90 Characters

КОМУС – ТОВАРЫ ДЛЯ ОФИСА И БИЗНЕСА: КУПИТЬ КАНЦТОВАРЫ, БУМАГУ, ХОЗТОВАРЫ, ПОДАРКИ И МЕБЕЛЬ

Meta Description 140 Characters

Комус - комплексная поставка товаров для офиса и бизнеса. Низкие цены и акции для малого, среднего и крупного бизнеса. Более 70 000 товаров.

Effective URL 20 Characters

https://www.komus.ru

Excerpt Page content

Комус – товары для офиса и бизнеса: купить канцтовары, бумагу, хозтовары, подарки и мебель ...

Keywords Cloud Density

область41 товары32 новинки19 мебель18 папки16 средства15 раздела14 комус14 бумага14 бизнеса12

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

Keyword	Freq	Title	Desc	Domain	H1	H2
область	41
товары	32
новинки	19
мебель	18
папки	16
средства	15
раздела	14
комус	14
бумага	14
бизнеса	12

Google Preview Your look like this in google search result

КОМУС – ТОВАРЫ ДЛЯ ОФИСА И БИЗНЕСА: КУПИТЬ КАНЦТОВАРЫ, БУМАГ

https://www.komus.ru

Robots.txt File Detected

http://komus.ru/robots.txt

Sitemap.xml File Detected

http://komus.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: 1998-09-23 / 22 years

Expires on: 2020-09-30 / 0 months 3 days

RU-CENTER-RU ,

Nameservers

ns1.linode.com.

ns2.linode.com.

ns3.linode.com.

ns4.linode.com.

ns5.linode.com.

Page Size Code & Text Ratio

Document Size: ~682.22 KB

Code Size: ~505.17 KB

Text Size: ~177.05 KB Ratio: 25.95%

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

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

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

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

Eliminate render-blocking resources Potential savings of 510 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 252 KB

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 888 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 30 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 270 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

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 89 KB

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

Speed Index 2.6 s

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

First CPU Idle 3.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).

Avoid enormous network payloads Total size was 3,915 KB

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

Minimize main-thread work 2.5 s

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

First Contentful Paint 0.8 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 10 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 3,889 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 183 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.8 s

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

Keep request counts low and transfer sizes small 122 requests • 3,915 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 23 resources found

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

Max Potential First Input Delay 360 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.3 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.1 s

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

Estimated Input Latency 60 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 12 KB

Minifying CSS files can reduce network payload sizes

Mobile

Serve images in next-gen formats Potential savings of 620 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 530 ms

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

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

Optimized images load faster and consume less cellular data

Enable text compression Potential savings of 708 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 660 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 1,280 ms

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

Reduce JavaScript execution time 4.8 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 813 KB

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

Speed Index 8.8 s

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

First CPU Idle 14.5 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).

Avoid enormous network payloads Total size was 2,738 KB

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

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

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

Avoid chaining critical requests 17 chains found

Avoid an excessive DOM size 3,342 elements

Minify JavaScript Potential savings of 31 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 5.1 s

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

Keep request counts low and transfer sizes small 114 requests • 2,738 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 11 resources found

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

Max Potential First Input Delay 1,130 ms

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

Time to Interactive 21.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 21.4 s

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

Estimated Input Latency 520 ms

First Contentful Paint (3G) 6642 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 9 KB

Minifying CSS files can reduce network payload sizes

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 99.73% 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 46 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

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 405 Method Not Allowed
Server: QRATOR
Date: Sun, 12 Jan 2020 18:00:09 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Keep-Alive: timeout=15
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Set-Cookie: JSESSIONID=C9FD72919F7CB1F42FBCE360C1929DE2.hybris7p.komus.net; Domain=.komus.ru; Expires=Tue, 11-Feb-2020 18:00:09 GMT; Path=/; Secure; HttpOnly
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Set-Cookie: CURRENT_REGION=77; Domain=.komus.ru; Expires=Tue, 10-Jun-2031 10:00:09 GMT; Path=/; HttpOnly
Allow: GET
Set-Cookie: JSESSIONID=C9FD72919F7CB1F42FBCE360C1929DE2.hybris7p.komus.net; Domain=.komus.ru; Expires=Tue, 11-Feb-2020 18:00:09 GMT; Path=/; Secure; HttpOnly
Strict-Transport-Security: max-age=31536000; includeSubDomains
Set-Cookie: _PXSTKY_=; Expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	komus.ru	178.248.237.25	IN	226
NS	komus.ru	ns5.linode.com	IN	86327
NS	komus.ru	ns4.linode.com	IN	86327
NS	komus.ru	ns2.linode.com	IN	86327
NS	komus.ru	ns3.linode.com	IN	86327
NS	komus.ru	ns1.linode.com	IN	86327
MX	komus.ru	aspmx.l.google.com	IN	300
MX	komus.ru	aspmx3.googlemail.com	IN	300
MX	komus.ru	aspmx2.googlemail.com	IN	300
MX	komus.ru	aspmx5.googlemail.com	IN	300
MX	komus.ru	alt2.aspmx.l.google.com	IN	300
MX	komus.ru	aspmx4.googlemail.com	IN	300
MX	komus.ru	alt1.aspmx.l.google.com	IN	300
TXT	komus.ru	bhg2hjh0s13bfn0fly5k205gplthkdcl	IN	300
TXT	komus.ru	v=spf1 ip4:130.193.66.100 ip4:130.193.66.124 +a:mhub2.komus.ru +mx include:_spf.google.com ~all	IN	300
TXT	komus.ru	201912020609344hwre2trxxxbc56wegckcxok459y6fsh2fsu3ya4iowcnxi0un	IN	300

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

47 komus.ru Last Updated: 8 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Google Tag Manager

Hybris

Java

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