Your Website Score is

Similar Ranking

29
REZULTATI: NOGOMET, 1. HNL, PREMIER LEAGUE, SPORTSKI REZULTATI UŽIVO, LIVESCORE
rezultati.com
29
BERANDA | PORTAL RESMI PEMERINTAH PROVINSI DKI JAKARTA
jakarta.go.id
29
ДНЕВНИК.РУ
dnevnik.ru
29
慕课网-程序员的梦工厂
imooc.com
29
有声小说,听小说,有声书,在线听书电台-喜马拉雅FM
ximalaya.com
29
VITUX - LINUX COMPENDIUM
vitux.com
29
СПОРТ.UA ⇔ СВЕЖИЕ НОВОСТИ СПОРТА ОНЛАЙН ⋆ ВСЕ ПРО СПОРТ УКРАИНЫ И МИРА НА СЕГОДНЯ
sport.ua

Latest Sites

14
OSLOWAY | YOUR BEST LOCAL TOURS AND EXPERIENCES IN OSLO
osloway.no
22
JUST A MOMENT...
hourlyminer.com
33
ピアノ教室ネット|先生との出会いはここから。全国のピアノ教室から検索!
pnet.kawai.jp
19
ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|
adagiettopiano.com
33
ГЛАВНАЯ | UNIEX
uniex.biz
23
AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING
ahmadimado.net
19
DOGESILVA LIMITED - HOME
dogesilva.com

Top Technologies

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

29 oriflame.ru Last Updated: 8 months

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

Desktop

Mobile

Performance Desktop Score 24%
Best Practices Desktop Score 54%
SEO Desktop Score 100%
Progressive Web App Desktop Score 27%
Performance Mobile Score 6%
Best Practices Mobile Score 54%
SEO Mobile Score 98%
Progressive Web App Mobile Score 30%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 37 Characters
ORIFLAME | ORIFLAME COSMETICS
Meta Description 199 Characters
Орифлэйм – одна из ведущих косметических компаний прямых продаж. Мы предлагаем широкий ассортимент высококачественных косметических средств и возможности для создания и развития собственного бизнеса.
Effective URL 23 Characters
https://www.oriflame.ru
Excerpt Page content
Oriflame | Oriflame Cosmetics ...
Keywords Cloud Density
уход47 средства34 бренды32 рейтинг23 продукты21 oriflame19 новинка18 волос18 макияж18 новинки15
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
уход 47
средства 34
бренды 32
рейтинг 23
продукты 21
oriflame 19
новинка 18
волос 18
макияж 18
новинки 15
Google Preview Your look like this in google search result
ORIFLAME | ORIFLAME COSMETICS
https://www.oriflame.ru
Орифлэйм – одна из ведущих косметических компаний прямых продаж. Мы предлагаем широкий ассортимент высококачественных косметических средств и возможно
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~380.9 KB
Code Size: ~245.68 KB
Text Size: ~135.22 KB Ratio: 35.50%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Serve images in next-gen formats Potential savings of 324 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
Reduce server response times (TTFB) Root document took 1,630 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 840 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 100 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 50 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 2,370 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 5.0 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 604 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 63 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.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).
Avoid enormous network payloads Total size was 3,436 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 8.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 1.5 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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 118 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 2,833 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 11 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 255 requests • 3,436 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 44 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,190 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 7.0 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 30.6 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 660 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
Remove unused CSS Potential savings of 51 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

Mobile

Mobile Screenshot
Time to Interactive 29.7 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
Page load is not fast enough on mobile networks Interactive at 29.7 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 3,320 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) 11553 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Tap targets are not sized appropriately 83% 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 99.28% 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 51 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 188 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
Reduce server response times (TTFB) Root document took 830 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 3,180 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 90 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 1,430 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 11,180 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 22.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 561 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
Speed Index 18.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 27.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).
Avoid enormous network payloads Total size was 3,016 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 31.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 5.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 1 vulnerability detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 118 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 2,840 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 11 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 5.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 241 requests • 3,016 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 41 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 4,630 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Length: 372431
Content-Type: text/html; charset=utf-8
Expires: -1
Set-Cookie: ru_website#lang=ru-RU; path=/
Set-Cookie: ASP.NET_SessionId=1uzl5dhnzlsr1z44cdjuxyxx; path=/; HttpOnly
Set-Cookie: UserKey=extranet\Anonymous; path=/
Set-Cookie: SC_ANALYTICS_GLOBAL_COOKIE=4e28b64ee82c47148e1ef8e93b3fa5ed|False; expires=Tue, 18-Dec-2029 20:46:34 GMT; path=/; HttpOnly
Set-Cookie: OriTracking=ee2a49d8-fa48-4fbc-b99a-0cfa0a5fc7bb; expires=Sun, 18-Dec-2039 20:46:34 GMT; path=/
Date: Wed, 18 Dec 2019 20:46:34 GMT
Set-Cookie: BIGipServerpool-live-cis-onl-web=285266442.20480.0000; path=/; Httponly; Secure
Set-Cookie: f5avraaaaaaaaaaaaaaaa_session_=INIMLCKLPCABPNOADJDHMHGHFKAGFBLEMIIMNHEMELBEDGAJHFIACDCICJAIHNLBNEADMKNLAPGGNLGKFBPAPHKFOIECJOEBCEDPMHMADNEGDFHENEFPHHIKBICIGNMG; HttpOnly; secure
Set-Cookie: TS01fd0901=014b5de84190f82bdc048345c41e2cade7cfa13db72eae8f3f989e9f1498c1c2ce2214218b91e4bccf8d49d6b5a61481ad7b31a7e4b3b89709d7cf822cbdaff3536160b85fdff3e7479cdd5ac92eef83c97de7880e8260019029a3f6134ab231064db6cc068f0cbc84a6c41d129763826255c35057ac123385c79169f48e86d322b998c439064c649afec62010fa43cbe087c3f0d35e3f40aae1a1a3e6ef885237f8ec5834; Path=/
Set-Cookie: TSd569cd1d027=08afc1cc77ab20009b1a82e662e625dc97d1b6d3a34429324b1e1b2b7b7de976b23fe6fbcccd524908e2c163ff1130001f6754c823556f32b4a02eb211147fd2082c47120f45c88f648b41c5fcde1edf173eb2f139c15da3ed4c8808feb73e88;Path=/
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome