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

Your Website Score is


Similar Ranking

39
v. II (beta) Скрипты качай бесплатно! PHP, шаблоны, самоучители, мультимедия,CMS, игры, форумы, разное, знакомства, раздачи, магазины!
4script.info
39
АУДИОКНИГИ СКАЧАТЬ БЕСПЛАТНО БЕЗ РЕГИСТРАЦИИ
abookz.net
39
Alldayklipart.ru - Все что нужно для дизайна и графики, авторские рамочки, оригинальные календари, векторные элементы, элемент дизайна, интерьер, фото клипарт, фоны, текстуры, исходники, открытки, фот
alldayklipart.ru
39
Скачать фильмы программы игры
associatcs.ru
39
Скачать игры бесплатно на телефон, бесплатные игры, игры на телефон скачать без регистрации
bestgamemobile.ru
39
BLOGIG.ORG - скачать бесплатно новые игры, фильмы на комп, музыку, программы, игры для консоли бесплатно без регистрации
blogig.org
39
c400.ru - Развлекательный портал
c400.ru

Latest Sites

19
СТОМАТОЛОГИЯ ИМПЛАНТ-ЭКСПЕРТ – ОФИЦИАЛЬНЫЙ САЙТ В МОСКВЕ
implant-expert.ru
2
ГЛАВНАЯ СТРАНИЦА
ti.capital
39
ТОВАРЫ ДЛЯ ВЗРОСЛЫХ | ИНТЕРНЕТ СЕКС-ШОП | MY-LOVESHOP.RU
my-loveshop.ru
31
ИНФОРМАЦИОННО-НОВОСТНОЙ ПОРТАЛ ГОРОДА СОЧИ
sochi.city
90
ИСТОРИЯ ЗМИЕВСКОГО КРАЯ – ГЛАВНАЯ
colovrat.at.ua

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

39 kwork.ru Last Updated: 4 months

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

Desktop

Mobile

Performance Desktop Score 93%
Best Practices Desktop Score 69%
SEO Desktop Score 100%
Progressive Web App Desktop Score 73%
Performance Mobile Score 57%
Best Practices Mobile Score 69%
SEO Mobile Score 96%
Progressive Web App Mobile Score 74%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Title Tag 70 Characters
ФРИЛАНС БИРЖА – РАБОТА ДЛЯ ФРИЛАНСЕРОВ НА САЙТЕ УДАЛЕННОЙ РАБОТЫ KWORK
Meta Description 350 Characters
Маркетплейс и биржа фриланс-услуг Kwork. Все услуги фрилансеров от 500 руб. Более 200 000 исполнителей. Четкие сроки, высокая скорость выполнения. Контроль качества, арбитраж в случае споров. 100% гарантия возврата средств в случае срыва заказа. Строгая система рейтингов исполнителей. В результате — в каталоге предложения только лучших фрилансеров.
Effective URL 16 Characters
https://kwork.ru
Excerpt Page content
Фриланс биржа – работа для фрилансеров на сайте удаленной работы Kwork РегистрацияВход На главную Каталог услугПравила сервисаВопрос - ОтветПерейти на полную версию сайта ...
Keywords Cloud Density
kwork13 дизайн11 реклама11 тексты10 фриланс9 сайта8 бизнес7 переводы7 услуг7 трафик7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
kwork 13
дизайн 11
реклама 11
тексты 10
фриланс 9
сайта 8
бизнес 7
переводы 7
услуг 7
трафик 7
Google Preview Your look like this in google search result
ФРИЛАНС БИРЖА – РАБОТА ДЛЯ ФРИЛАНСЕРОВ НА САЙТЕ УДАЛЕННОЙ РА
https://kwork.ru
Маркетплейс и биржа фриланс-услуг Kwork. Все услуги фрилансеров от 500 руб. Более 200 000 исполнителей. Четкие сроки, высокая скорость выполнения. Кон
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: 2015-07-31 / 5 years
Expires on: 2020-07-31 / 1 months 20 days

REGRU-RU ,

Nameservers
ns1.mirahost.ru.
ns2.mirahost.ru.
Page Size Code & Text Ratio
Document Size: ~114.99 KB
Code Size: ~93.19 KB
Text Size: ~21.79 KB Ratio: 18.95%

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
Remove unused CSS Potential savings of 124 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 172 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 220 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 0 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 90 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 80 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
Defer offscreen images Potential savings of 17 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.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 1,482 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.1 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.7 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 12 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 963 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 4 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 74 requests • 1,482 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 37 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.1 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
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
Avoid chaining critical requests 8 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 986 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)
Preload key requests Potential savings of 5,700 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
First Meaningful Paint 4.1 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 67 requests • 1,391 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 33 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 650 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 9.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
First Contentful Paint (3G) 4930 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 not sized appropriately 57% 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 98.5% 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 123 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 66 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 190 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 10 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce the impact of third-party code Third-party code blocked the main thread for 340 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 570 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.1 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 17 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 4.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.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 1,391 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.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 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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