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

Your Website Score is


Similar Ranking

32
Новости дня на agaroza.ru
agaroza.ru
32
ATD - обозреватель новинок автопрома, тест-драйвы.
all-test-drives.com
32
Astronomical Net of Ukraine - Астрономическая Сеть Украины
astronomy.net.ua
32
Смотреть онлайн бесплатно --- фильмы с участием знаменитостей - coii.ru
coii.ru
32
Более 1000 шаблонов DLE и Joomla, скачивание без файлообменников
dle-joomla.ru
32
Документальные фильмы онлайн
dokonline.com
32
Электронная библиотека Dony
dony.ru

Latest Sites

14
ДОСТАВКА ЕДЫ
mr-cook.ru
19
FOODIE БЫСТРАЯ ДОСТАВКА ВКУСНОЙ ЕДЫ В СИМФЕРОПОЛЕ ЗАКАЗАТЬ ЕДУ
foodie-eda.ru
54
ЗАПЧАСТИ НА ТЕХНИКУ Т-170 Т-130 Б-10 | СПЕЦДОРТРАК ДЗ-98
trak74.ru
19
PUBLIC ORDER AND SAFETY IN TODAY'S WORLD
orderandsafety.org
31
АВТОСЕРВИС «REFRESH-ISTRA»
refresh-istra.ru
22
ᐈ КОМПЬЮТЕРНЫЙ МАСТЕР ДЛЯ НАСЕЛЕНИЯ — С ВЫЕЗДОМ НА ДОМ В МИНСКЕ
compdoc.by
19
HOSTINGS.GE - WEB HOSTING
hostings.ge

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

32 f-prime.ru Last Updated: 4 months

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

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 69%
SEO Desktop Score 100%
Progressive Web App Desktop Score 58%
Performance Mobile Score 70%
Best Practices Mobile Score 69%
SEO Mobile Score 99%
Progressive Web App Mobile Score 56%
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 43 Characters
ФОТОПРАЙМ | ПРОИЗВОДСТВО ФОТОРАМОК И БАГЕТА
Meta Description 86 Characters
Производство пластикового багета, пластиковых и деревянных фоторамок от производителя.
Effective URL 18 Characters
https://f-prime.ru
Excerpt Page content
ФотоПрайм | Производство фоторамок и багета ФотоПрайм Производство фоторамок и багета Перейти к содержимому О компании Продукция Оптовикам Производство Контакты ФотоПрайм Наше пред...
Keywords Cloud Density
ширина8 высота8 багета4 производство4 фоторамки4 багет4 фотопрайм3 производим3 пластик3 15мм3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
ширина 8
высота 8
багета 4
производство 4
фоторамки 4
багет 4
фотопрайм 3
производим 3
пластик 3
15мм 3
Google Preview Your look like this in google search result
ФОТОПРАЙМ | ПРОИЗВОДСТВО ФОТОРАМОК И БАГЕТА
https://f-prime.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: 1970-01-01 / 51 years
Create on: 2016-06-01 / 4 years
Expires on: 2020-06-01 / 3 months 22 days

R01-RU ,

Nameservers
ns1.timeweb.ru.
ns2.timeweb.ru.
ns3.timeweb.org.
ns4.timeweb.org.
Page Size Code & Text Ratio
Document Size: ~38.52 KB
Code Size: ~24.16 KB
Text Size: ~14.36 KB Ratio: 37.28%

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
Defer offscreen images Potential savings of 149 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 197 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 1.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).
Avoids enormous network payloads Total size was 815 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.8 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.9 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 19 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 275 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 Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 59 requests • 815 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 13 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 70 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.8 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
Serve images in next-gen formats Potential savings of 111 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 200 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 92 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 9 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 60 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 20 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

Mobile

Mobile Screenshot
Server response times are low (TTFB) Root document took 130 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,930 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 9 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 57 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 710 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.4 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 217 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 51 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.1 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 669 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.6 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.6 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 19 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 275 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 Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 56 requests • 669 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 14 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 270 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.8 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) 5091.5 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 100 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 92% 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
Serve images in next-gen formats Potential savings of 86 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

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