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

Your Website Score is


Similar Ranking

19
WEBART45 - РАЗРАБОТКА САЙТОВ И ВЕБ-СЕРВИСОВ: ЛЕНДИНГИ, КОРПОРАТИВНЫЕ ПОРТАЛЫ, ИНТЕРНЕТ-МАГАЗИНЫ, СОЦИАЛЬНЫЕ СЕТИ, СТАРТАПЫ.
webart45.ru
19
Доставка суши, роллов, пиццы, блюд японской кухни
city-sushi.com
19
AllBestLib.ru - купить и скачать книги, хорошее качество
allbestlib.ru
19
Студия "Барс". Бесплатные футажи, бесплатные проекты After Effects, проекты PhotoShop многое другое.
barsart.ru
19
Смотреть онлайн и скачать 3D фильмы бесплатно
bd3d.su
19
ДОМЕН НЕ ПРИЛИНКОВАН НИ К ОДНОЙ ИЗ ДИРЕКТОРИЙ НА СЕРВЕРЕ!
blu-r-video.com
19
ДОМЕН НЕ ПРИЛИНКОВАН НИ К ОДНОЙ ИЗ ДИРЕКТОРИЙ НА СЕРВЕРЕ!
dl1second.com

Latest Sites

19
КЛИНИКА ЭСТЕТИЧЕСКОЙ МЕДИЦИНЫ В МОСКВЕ - КОСМЕТОЛОГИЯ & СТОМАТОЛОГИЯ ДОКТОРА КОРЧАГИНОЙ
k-clinic.ru
31
ИНТЕРНЕТ МАГАЗИН АВТОЗАПЧАСТЕЙ SPPARTS.RU | КУПИТЬ ЗАПЧАСТИ ДЛЯ ИНОМАРОК В МОСКВЕ
spparts.ru
19
ДВИГАТЕЛЯ РЕМОНТ ДВС, МИНСК. БЕНЗИН + ДИЗЕЛЬ. ЦЕНЫ 2020.
dvigok.by
14
MFU-MARKET.RU
mfu-market.ru
2
СНТ АКМИГРАН – ОФИЦИАЛЬНЫЙ САЙТ
akmigran.ru
19
ГЛАВНАЯ СТРАНИЦА - ТЕЛЕКАНАЛ «НАУКА»
naukatv.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

19 10dress.ru Last Updated: 1 day

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

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 79%
SEO Desktop Score 91%
Progressive Web App Desktop Score 56%
Performance Mobile Score 32%
Best Practices Mobile Score 71%
SEO Mobile Score 92%
Progressive Web App Mobile Score 54%
Only Registered Users

Sign up for see all features and reviews about this site

Login
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 39 Characters
ИНТЕРНЕТ-МАГАЗИН БЕЛОРУССКОГО ТРИКОТАЖА
Meta Description 131 Characters
Интернет-магазин белорусского трикотажа . Доставка по России от 1 шт. наложенный платёж , Почта России , СДЭК , EMS , опт розница
Effective URL 18 Characters
https://10dress.ru
Excerpt Page content
Интернет-магазин белорусского трикотажа ...
Keywords Cloud Density
наличии82 ликвидация46 подробнее42 быстрый41 просмотр41 1 29028 платье24 одежда13 условия13 модель10
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
наличии 82
ликвидация 46
подробнее 42
быстрый 41
просмотр 41
1 290 28
платье 24
одежда 13
условия 13
модель 10
Google Preview Your look like this in google search result
ИНТЕРНЕТ-МАГАЗИН БЕЛОРУССКОГО ТРИКОТАЖА
https://10dress.ru
Интернет-магазин белорусского трикотажа . Доставка по России от 1 шт. наложенный платёж , Почта России , СДЭК , EMS , опт розница
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~917.29 KB
Code Size: ~514.43 KB
Text Size: ~402.86 KB Ratio: 43.92%

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
Avoid chaining critical requests 24 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
Defer offscreen images Potential savings of 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Keep request counts low and transfer sizes small 58 requests • 1,263 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift 0.01
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid an excessive DOM size 4,295 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)
Max Potential First Input Delay 330 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve images in next-gen formats Potential savings of 168 KiB
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
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
Efficiently encode images Potential savings of 58 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Remove unused JavaScript Potential savings of 223 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Serve static assets with an efficient cache policy 41 resources found
A long cache lifetime can speed up repeat visits to your page
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
Reduce initial server response time Root document took 740 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Potential savings of 900 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minimize third-party usage Third-party code blocked the main thread for 20 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
JavaScript execution time 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Remove unused CSS Potential savings of 114 KiB
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
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Speed Index 1.8 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. [Learn more](https://web.dev/first-cpu-idle/).
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoids enormous network payloads Total size was 1,263 KiB
Large network payloads cost users real money and are highly correlated with long load times

Mobile

Mobile Screenshot
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoids enormous network payloads Total size was 1,095 KiB
Large network payloads cost users real money and are highly correlated with long load times
Estimated Input Latency 1,170 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
Time to Interactive 9.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused JavaScript Potential savings of 212 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Max Potential First Input Delay 1,950 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid an excessive DOM size 4,295 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 CPU Idle 8.3 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/).
Defer offscreen images Potential savings of 25 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Document uses legible font sizes 99.3% 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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests 22 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 serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Serve images in next-gen formats Potential savings of 168 KiB
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 long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
First Contentful Paint (3G) 8490 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Meaningful Paint 3.8 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy 38 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.005
Cumulative Layout Shift measures the movement of visible elements within the viewport
Efficiently encode images Potential savings of 58 KiB
Optimized images load faster and consume less cellular data
Remove unused CSS Potential savings of 115 KiB
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
Total Blocking Time 1,560 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Minimize main-thread work 6.8 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 largest contentful element painted within the viewport
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
Largest Contentful Paint 5.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 2,470 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index 6.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First Contentful Paint 3.8 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Keep request counts low and transfer sizes small 55 requests • 1,095 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Reduce initial server response time Root document took 720 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce the impact of third-party code Third-party code blocked the main thread for 560 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
Reduce JavaScript execution time 4.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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