Your Website Score is

Similar Ranking

88
CLEAN, OPTIMIZE, SPEED UP AND SECURE PC ----WARE DOWNLOAD - IOBIT
iobit.com
88
Ҳ-Ϲٷ콢-ÈTMALL.COM
watsons.tmall.com
88
SPORT | NOTICIAS DEL BARÇA, LA LIGA, FÚTBOL Y OTROS DEPORTES
sport.es
88
Ҳ-DIDIBOYٷ콢-ÈTMALL.COM
didiboy.tmall.com
88
LEARN THE LATEST TECH SKILLS; ADVANCE YOUR CAREER | UDACITY
udacity.com
88
天猫食品-理想生活上天猫
food.tmall.com
88
店铺浏览-淘宝网
honeys.tmall.com

Latest Sites

14
EARN $1000 AND MORE PER DAY!
newcrypto.world
40
İSTANBUL SPOR ENVANTERI | İBB DIRECTORATE OF YOUTH AND SPORTS
sporenvanteri.ibb.istanbul
19
FREEMINING - START--- BITCOIN CLOUD MINING & EARN--- BTC EVERY HOUR
freemining.club
19
MININGCOMPANY.LTD - CLOUD MINING FARMA
miningcompany.ltd
26
NACIONAL MONTE DE PIEDAD
montepiedad.com.mx
19
PINOY MOVIES - WATCH PINOY MOVIES ONLINE---
cineko.to
14
FINYA LIMITED
finyalimited.com

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

88 2gis.ru Last Updated: 1 year

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 40%
Best Practices Desktop Score 62%
SEO Desktop Score 91%
Progressive Web App Desktop Score 31%
Performance Mobile Score 48%
Best Practices Mobile Score 69%
SEO Mobile Score 85%
Progressive Web App Mobile Score 59%
Page Authority Authority 62%
Domain Authority Domain Authority 90%
Moz Rank 6.2/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 81 Characters
КАРТА ГОРОДОВ РОССИИ: МОСКВА, САНКТ-ПЕТЕРБУРГ, НОВОСИБИРСК И ДРУГИЕ ГОРОДА — 2ГИС
Meta Description 113 Characters
Подробная карта городов России: поиск по адресу, телефоны, отзывы, фото, часы работы фирм и удобный поиск проезда
Effective URL 15 Characters
https://2gis.ru
Excerpt Page content
Карта городов России: Москва, Санкт-Петербург, Новосибирск и другие города — 2ГИС ...
Keywords Cloud Density
2гис5 интересное2 лицензионное2 соглашение2 обратная2 связь2 путеводитель2 реклама2 2gis1 красота1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
2гис 5
интересное 2
лицензионное 2
соглашение 2
обратная 2
связь 2
путеводитель 2
реклама 2
2gis 1
красота 1
Google Preview Your look like this in google search result
КАРТА ГОРОДОВ РОССИИ: МОСКВА, САНКТ-ПЕТЕРБУРГ, НОВОСИБИРСК И
https://2gis.ru
Подробная карта городов России: поиск по адресу, телефоны, отзывы, фото, часы работы фирм и удобный поиск проезда
Robots.txt File Detected
Sitemap.xml File Detected
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-02-18 / 20 years
Expires on: 2020-02-19 / 9 months 16 days

RU-CENTER-RU ,

Nameservers
ns2.2gis.com.
ns.2gis.com.
ns3.2gis.com.
Page Size Code & Text Ratio
Document Size: ~172.49 KB
Code Size: ~35.54 KB
Text Size: ~136.95 KB Ratio: 79.40%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Reduce JavaScript execution time 2.6 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 5.4 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.9 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,751 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 7.4 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.3 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 4 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 363 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 0.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 88 requests • 2,751 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 8 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 720 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.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 on simulated mobile network at 30.5 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 230 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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Serve images in next-gen formats Potential savings of 472 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 1,390 ms
Time To First Byte identifies the time at which your server sends a response
Minimize third-party usage Third-party code blocked the main thread for 60 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,740 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Mobile

Mobile Screenshot
First Meaningful Paint 2.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 109 requests • 1,436 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 22 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 350 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 8.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
First Contentful Paint (3G) 5190 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 150 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
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 doesn't use legible font sizes 21.93% 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 29 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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Serve images in next-gen formats Potential savings of 408 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 780 ms
Redirects introduce additional delays before the page can be loaded
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 870 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 220 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 920 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
Speed Index 7.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.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,436 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.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 2.6 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 6 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 866 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)

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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 19:03:11 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Vary: User-Agent
Vary: Accept-Language
Cache-Control: no-transform, no-store, no-cache, must-revalidate, max-age=0
Pragma: no-cache
X-Content-Type-Options: nosniff
X-XSS-Protection: 1
X-Frame-Options: deny
Set-Cookie: dg5_flags=; Max-Age=662256000; Path=/; Expires=Tue, 20 Nov 2040 19:03:11 GMT
Set-Cookie: dscnt=1; Path=/; Expires=Tue, 20 Nov 2040 19:03:11 GMT
Set-Cookie: _2gis_webapi_session=a458370c-0768-4f56-a89b-3fb8df87d6b4; Path=/
Set-Cookie: _2gis_webapi_user=5a7bf888-0115-4874-95bc-89565d18cb38; Path=/; Expires=Tue, 20 Nov 2040 19:03:11 GMT
Set-Cookie: openBeta=1; Max-Age=662256000; Domain=.2gis.ru; Path=/; Expires=Tue, 20 Nov 2040 19:03:11 GMT
Server-Timing: a0;desc="3. restore";dur=161,a1;desc="5. render";dur=11,a2;desc="region/detect";dur=26,a3;desc="market/fetch_project_branches";dur=23,a4;desc="entity/fetch_profile_no_type";dur=97,a5;desc="gta/fetch_dashboard_gta";dur=10,a6;desc="rubric/fetch_dashboard";dur=13
X-Concurrent-Requests: 2
ETag: W/"2aae3-9nnYwgIJ3TELslv2GF2/m+kiVPA"
X-Request-Id: 60eaf3602dee62f0b5cb692c9433db21
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome