Разместите свои услуги бесплатно
Техническая поддержка
Помогите рублём проекту

Your Website Score is

Similar Ranking

24
Дешевые авиабилеты онлайн, цены. Поиск билетов на самолет и сравнение цен — Aviasales.ru
alpod.ru
24
Скачать аниме на ---BOX
---box.com.ua
24
Умный баран - программы, книги и медиа-файлы
barandok.ru
24
მიუნხენის "ბაიერნის" ქართული ფან-კლუბი
bayern.ge
24
Торговое оборудование в СПб для магазина: собственное производство
proekt-d.ru
24
Новости из Испании: Барселона и Каталония
colinfo.ru
24
Электронная клубная музыка :: CosmoVolume.com
cosmovolume.com

Latest Sites

12
ТОП 10: ЧТО ТАКОЕ БЫСТРЫЕ ---? ОФОРМИТЬ ОНЛАЙН-ЗАЯВКУ НА --- БЕЗ СПРАВОК
transportified.ru
45
ГЛАВНАЯ - ГРАФАРИКИ
grafariki.ru
12
ТОП 10: ВИДЫ И ФОРМЫ ---ОВ В БАНКАХ | ЛУЧШИЕ ПРЕДЛОЖЕНИЯ | ОФОРМИТЬ ОНЛАЙН-ЗАЯВКУ НА --- БЕЗ СПРАВОК
undard.ru
19
АКВАПАРК ЛЕТОЛЕТО ТЮМЕНЬ - ЦЕНЫ НА 2020 ГОД | АКЦИИ
letoleto-tyumen.ru
12
ДОМЕН GENTILE.RU: КУПИТЬ В МАГАЗИНЕ ДОМЕННЫХ ИМЕН REG.RU
gentile.ru
19
LAST CHAOS REVOLUTION СLASSIC НОВЫЙ СЕРВЕР
lastchaos-revol.ru

Top Technologies

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

24 traingames.ru Last Updated: 3 months

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

Desktop

Mobile

Performance Desktop Score 97%
Best Practices Desktop Score 62%
SEO Desktop Score 90%
Progressive Web App Desktop Score 37%
Performance Mobile Score 51%
Best Practices Mobile Score 62%
SEO Mobile Score 83%
Progressive Web App Mobile Score 39%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: WINDOWS-1251
Title Tag 10 Characters
METROGAMES
Meta Description 0 Characters
NO DATA
Effective URL 20 Characters
http://traingames.ru
Excerpt Page content
Metrogames Профилактические работы на сервисе. Часть функционала может быть недоступна некоторое время. Metrogames ...
Keywords Cloud Density
metrogames6 форум4 mobile3 traktorist3 сообщений2 сегодня2 всего2 пользователей2 здесь2 активны1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
metrogames 6
форум 4
mobile 3
traktorist 3
сообщений 2
сегодня 2
всего 2
пользователей 2
здесь 2
активны 1
Google Preview Your look like this in google search result
METROGAMES
http://traingames.ru
Metrogames Профилактические работы на сервисе. Часть функционала может быть недоступна некоторое время. Metrogames ...
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: 2017-12-29 / 3 years
Expires on: 2019-12-29 / 8 months 24 days

RD-RU ,

Nameservers
ns1.q11.ru.
ns2.q11.ru.
Page Size Code & Text Ratio
Document Size: ~18.55 KB
Code Size: ~9.28 KB
Text Size: ~9.27 KB Ratio: 49.98%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

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
Minimizes main-thread work 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First CPU Idle 1.2 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).
Time to Interactive 1.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 20 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 18 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
JavaScript execution time 0.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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Eliminate render-blocking resources Potential savings of 110 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 130 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
Does not use HTTPS 40 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
Keep request counts low and transfer sizes small 141 requests • 671 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Initial server response time was short Root document took 250 ms
Keep the server response time for the main document short because all other requests depend on it
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
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 182 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 Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
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
Remove unused JavaScript Potential savings of 259 KB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint element 1 element found
This is the element that was identified as the Largest Contentful Paint
Serve images in next-gen formats Potential savings of 9 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
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Minify JavaScript Potential savings of 7 KB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoids enormous network payloads Total size was 671 KB
Large network payloads cost users real money and are highly correlated with long load times

Mobile

Mobile Screenshot
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
Avoids an excessive DOM size 171 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)
Document doesn't use legible font sizes 4.01% 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
First Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible
First CPU Idle 6.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).
Reduce the impact of third-party code Third-party code blocked the main thread for 1,020 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
Max Potential First Input Delay 400 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Serve static assets with an efficient cache policy 23 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 7.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 1,100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Keep request counts low and transfer sizes small 77 requests • 708 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short Root document took 260 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 18 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 enormous network payloads Total size was 708 KB
Large network payloads cost users real money and are highly correlated with long load times
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
Cumulative Layout Shift 0.052
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minify JavaScript Potential savings of 7 KB
Minifying JavaScript files can reduce payload sizes and script parse time
Enable text compression Potential savings of 24 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
Defer offscreen images Potential savings of 6 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve images in next-gen formats Potential savings of 9 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
Minimize main-thread work 4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Does not use HTTPS 42 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
Remove unused JavaScript Potential savings of 282 KB
Remove unused JavaScript to reduce bytes consumed by network activity
Estimated Input Latency 130 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) 4867.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce JavaScript execution time 2.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element 1 element found
This is the element that was identified as the Largest Contentful Paint

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Only Registered Users

Sign up for see all features and reviews about this site

Login

Comments