Your Website Score is

Similar Ranking

6
ГЛАВНАЯ
star-bus.ru
4
КИНО АФИША — ВСЁ, ЧТО ТЫ ИЩЕШЬ!
kino-afisha.ru
3
Muebles Cassius
mueblescassius.com.ar
2
COLORLANG.COM – ИЗУЧЕНИЕ АНГЛИЙСКОГО С НУЛЯ ОНЛАЙН
colorlang.com

Latest Sites

54
КУПИТЬ МЕДИЦИНСКУЮ СПРАВКУ В МОСКВЕ С ДОСТАВКОЙ!
spravkidok.com
23
VIRTUAL ASSISTANT | VIRTUAL EMPLOYEE| REMOTE STAFFING AGENCY| HIRE OFFSHORE STAFF
virtualteamindia.com
22
ЗАПЧАСТИ ДЛЯ СЕЛЬХОЗТЕХНИКИ КУПИТЬ В УКРАИНЕ В ИНТЕРНЕТ-МАГАЗИНЕ ВЕРХАГРО
verhagro.com.ua
12
ПЕСОК КАРЬЕРНЫЙ МЫТЫЙ В ПУШКИНО С ДОСТАВКОЙ ПО НИЗКОЙ ЦЕНЕ ДЛЯ СТЯЖКИ ДРЕНАЖА ПОДСЫПКИ БЕТОНА СТРОИТЕЛЬНЫЙ ПЕСОК КВАРЦЕВЫЙ САМОСВАЛОМ
pushkino-pesok.ru
21
MICSUPPORT - BEST IT COMPANY IN USA
micsupport.com
14
NOTICIAS DE ALTA TECNOLOGÍA
blogdealtatecnologia.blogspot.com

Top Technologies

Nginx
Web Servers
Google Font API
Font Scripts
WordPress
CMS
Font Awesome
Font Scripts
Apache
Web Servers
Twitter Bootstrap
Web Frameworks
Yoast SEO
SEO
Liveinternet
Analytics

6 star-bus.ru Last Updated: 3 months

Success 47% of passed verification steps
Warning 23% of total warning
Errors 30% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 85%
SEO Desktop Score 80%
Progressive Web App Desktop Score 27%
Performance Mobile Score 43%
Best Practices Mobile Score 85%
SEO Mobile Score 81%
Progressive Web App Mobile Score 30%
Page Authority Authority 12%
Domain Authority Domain Authority 3%
Moz Rank 1.2/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 7 Characters
ГЛАВНАЯ
Meta Description 0 Characters
NO DATA
Effective URL 19 Characters
https://star-bus.ru
Excerpt Page content
Главная Меню Главная ...
Meta Keywords 1 Detected
Keywords Cloud Density
казань29 билеты26 санкт23 москва22 екатеринбург20 краснодар20 петербург19 воронеж17 цена14 онлайн9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
казань 29
билеты 26
санкт 23
москва 22
екатеринбург 20
краснодар 20
петербург 19
воронеж 17
цена 14
онлайн 9
Google Preview Your look like this in google search result
ГЛАВНАЯ
https://star-bus.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: 1969-12-31 / 50 years
Create on: 2019-03-23 / 8 months
Expires on: 2020-03-23 / 4 months 2 days

RU-CENTER-RU ,

Nameservers
ns1.beget.com.
ns1.beget.pro.
ns2.beget.com.
ns2.beget.pro.
Page Size Code & Text Ratio
Document Size: ~100.86 KB
Code Size: ~69.51 KB
Text Size: ~31.35 KB Ratio: 31.09%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

1,914
Unique Visits
Daily
3,540
Pages Views
Daily
$2
Income
Daily
53,592
Unique Visits
Monthly
100,890
Pages Views
Monthly
$50
Income
Monthly
620,136
Unique Visits
Yearly
1,189,440
Pages Views
Yearly
$528
Income
Yearly

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

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

Desktop

Desktop Screenshot
Remove unused CSS Potential savings of 36 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 1,253 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 850 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Third-Party Usage 8 Third-Parties Found
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 60 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
Properly size images Potential savings of 1,099 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input
Avoids enormous network payloads Total size was 2,634 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.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 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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize Critical Requests Depth 32 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 814 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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 50 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 62 requests • 2,634 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 47 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 1.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 on simulated mobile network at 11.0 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

Mobile

Mobile Screenshot
Avoids enormous network payloads Total size was 2,633 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.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 2.4 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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minimize Critical Requests Depth 32 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 814 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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 50 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 62 requests • 2,633 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 47 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 11.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 at 11.3 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 160 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
First Contentful Paint (3G) 4695 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 85% 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 100% 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 34 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 1,253 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 810 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,830 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Third-Party Usage 8 Third-Parties Found
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 790 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.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 1,085 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 1,047 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 7.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

712,208

Global Rank

59,710

Russia
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
server: nginx-reuseport/1.13.4
date: Tue, 03 Sep 2019 14:55:05 GMT
content-type: text/html; charset=UTF-8
x-powered-by: PHP/7.2.16
p3p: policyref="/bitrix/p3p.xml", CP="NON DSP COR CUR ADM DEV PSA PSD OUR UNR BUS UNI COM NAV INT DEM STA"
x-powered-cms: Bitrix Site Manager (bc66eaf73d85797e7b499d9620554122)
set-cookie: PHPSESSID=3d193757f9dd6c9b456c9d5d1079c69e; path=/; domain=star-bus.ru; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: BITRIX_SM_ABTEST_s1=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; domain=star-bus.ru
content-encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments