Оценка вашего веб-сайта

Similar Ranking

1
zaruba.shop
1
serferclick.ru
1
priorbank.by
1
movie2freethai.com
1
adultfilmler.org
1
cad.skin

Latest Sites

26
ОБЗОРЫ НОВИНОК ТЕХНИКИ -
eurotehnik.ru
31
ТЕХНО SHIFT – РЕМОНТ НОУТБУКОВ ПК И СМАРТФОНОВ
kevin-seoshnik.ru
31
DOUGHNUT LOUNGE | SAVOR THE FLAVOR, LOVE THE LOUNGE
doughnutlounge.com
1
-
cad.skin
1
-
adultfilmler.org
1
-
priorbank.by
1
-
movie2freethai.com

1 cad.skin Last Updated: 2 weeks

Success 39% of passed verification steps
Warning 23% of total warning
Errors 38% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 47%
Best Practices Desktop Score 79%
SEO Desktop Score 100%
Performance Mobile Score 56%
Best Practices Mobile Score 79%
SEO Mobile Score 100%
Page Authority Authority 0%
Авторитет домена Авторитет домена 0%
Moz Rank 0.0/10
Показатель отказов Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 15 Characters
http://cad.skin
Excerpt Page content
require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );
Google Preview Your look like this in google search result
cad.skin
http://cad.skin
require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );
Robots.txt File Detected
http://cad.skin/robots.txt
Sitemap.xml File Detected
http://cad.skin/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~228 B
Code Size: ~17 B
Text Size: ~211 B Ratio: 92.54%

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Largest Contentful Paint 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused JavaScript Est savings of 1,391 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Render blocking requests Est savings of 10 ms
Requests are blocking the page's initial render, which may delay LCP
Improve image delivery Est savings of 482 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Avoid enormous network payloads Total size was 3,906 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid multiple page redirects Est savings of 220 ms
Redirects introduce additional delays before the page can be loaded
Speed Index 3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Est 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
Preload Largest Contentful Paint image Est savings of 40 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
Total Blocking Time 640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 15 resources found
A long cache lifetime can speed up repeat visits to your page
Font display Est savings of 360 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Time to Interactive 5.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies 40 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
Reduce unused CSS Est savings of 42 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Serve images in next-gen formats Est savings of 480 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Document request latency Est savings of 270 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Does not use HTTPS 14 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 served over 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
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Reduce the impact of third-party code Third-party code blocked the main thread for 740 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
Minimize main-thread work 4.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Use efficient cache lifetimes Est savings of 142 KiB
A long cache lifetime can speed up repeat visits to your page
Network Round Trip Times 10 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
Minify CSS Est savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Avoid long main-thread tasks 17 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid serving legacy JavaScript to modern browsers Est savings of 1 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Avoids an excessive DOM size 203 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)
Largest Contentful Paint element 3,840 ms
This is the largest contentful element painted within the viewport
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

Mobile

Mobile Screenshot
Largest Contentful Paint 26.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Use efficient cache lifetimes Est savings of 269 KiB
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 26,200 ms
This is the largest contentful element painted within the viewport
Minimizes main-thread work 1.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 Est savings of 1 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Document request latency Est savings of 130 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Time to Interactive 26.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 203 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)
Reduce unused JavaScript Est savings of 1,397 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Initial server response time was short Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Improve image delivery Est savings of 1,775 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Speed Index 10.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Does not use HTTPS 14 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 served over 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
Total Blocking Time 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Est 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
Reduce unused CSS Est savings of 30 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Preload Largest Contentful Paint image Est savings of 760 ms
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP
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
Serve images in next-gen formats Est savings of 1,656 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minimize third-party usage Third-party code blocked the main thread for 120 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
Server Backend Latencies 40 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
Document uses legible font sizes 69.1% 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
Serve static assets with an efficient cache policy 15 resources found
A long cache lifetime can speed up repeat visits to your page
Font display Est savings of 370 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Render blocking requests Est savings of 270 ms
Requests are blocking the page's initial render, which may delay LCP
Properly size images Est savings of 1,253 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minify CSS Est savings of 5 KiB
Minifying CSS files can reduce network payload sizes
First Contentful Paint 10.2 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid enormous network payloads Total size was 5,124 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid multiple page redirects Est savings of 760 ms
Redirects introduce additional delays before the page can be loaded

Speed And Optimization Tips

Скорость веб-сайта оказывает огромное влияние на производительность, влияя на пользовательский опыт, коэффициенты конверсии и даже рейтинг. Уменьшая время загрузки страницы, пользователи с меньшей вероятностью будут отвлекаться, а поисковые системы с
Title сайта
Предупреждение! Ваш заголовок не оптимизирован
Description сайта
Предупреждение! Ваше описание не оптимизировано
Robots.txt
Поздравляю! На вашем сайте есть файл robots.txt
Sitemap.xml
Поздравляю! Мы нашли файл карты сайта для вашего сайта
SSL безопасный
Поздравляю! Ваш сайт поддерживает HTTPS
Заголовки
Предупреждение! На вашей странице нет заголовков H1 и H2. Заголовки H1 и H2 помогают указать поисковым системам важные темы вашей страницы.
Черный список
Поздравляю! Ваш сайт не занесен в черный список
Валидатор W3C
Предупреждение! На вашем сайте есть ошибки W3C
Ускоренные мобильные страницы (AMP)
Предупреждение! У вашего сайта нет AMP-версии
Авторитет домена
Предупреждение! Авторитет домена вашего сайта медленный. Хорошо иметь авторитет домена больше 25.
GZIP Сжатие
Предупреждение! Ваш сайт не сжат, это может замедлить реакцию посетителей.
Favicon
Предупреждение! На вашем сайте нет значка favicon
Неработающие ссылки
Поздравляю! У вас нет битых ссылок Просмотр ссылок
First 0 Links Отношение HTTP статус

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Поиск

Информационный Сервер

Response Header Заголовки HTTP несут информацию о браузере клиента, запрашиваемой странице и сервере. 
HTTP/1.1 200 OK
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
Content-Type: text/html
Last-Modified: Thu, 19 Jun 2025 03:19:57 GMT
Accept-Ranges: bytes
Content-Encoding: gzip
Vary: Accept-Encoding
Content-Length: 200
Date: Sun, 13 Jul 2025 11:55:58 GMT
Записи DNS Записи ресурсов DNS, связанные с именем хоста
Просмотр записей DNS
Type Name Value Class TTL
A cad.skin 199.80.53.4 IN 9067
NS cad.skin ns2.fozzy.com IN 73199
NS cad.skin ns1.fozzy.com IN 51080
MX cad.skin cad.skin IN 10689
TXT cad.skin v=spf1 ip4:199.80.53.4 +a +mx ~all IN 13066
TXT cad.skin google-site-verification=PI3OdosYw0TS2eSzf4Hl8poEutbSrQgKt0QiqFV6VDU IN 12023

О нас

Контактная информация

Подписывайтесь на нас

Copyright 2016
Языки | English