Urbandecay.Ru - Website Report

Urbandecay.Ru

Traffic estimate for Urbandecay.ru is about 301 unique visits and 903 page views per day. Each unique visitor makes about 3 page views on average. According to traffic estimate, Urbandecay.ru should earn about $2.29 per day from the advertising revenue, which implies that this website is worth about $919.08. Alexa Traffic Rank estimates that it is ranked number 895,498 in the world and 0.00043% of global Internet users are visiting Urbandecay.ru on a regular basis. Website hosting location for Urbandecay.ru is: Chekhov, MOS, 142300, Russia. Server IP address: 217.74.40.46


About - urbandecay.ru

Edit WebSite Info

Earnings Report

Website Value: $919.08
Daily Revenue: $2.29
Monthly Revenue: $68.93
Yearly Revenue: $838.66

Traffic Report

Daily Unique Visitors: 301
Monthly Unique Visitors: 9,030
Daily Pageviews: 903 (3 per day)
Montly Pageviews: 27,090
Daily PageViews Per User: 3
Alexa Global Rank: 895,498
Alexa Reach: 0.00043% of global Internet users
Alexa Backlinks: 49
Average Page Load Time: 1,918

Country Report

Country Alexa Rank PageViews Visitors
Russia 73254 86.2% 82.7%
Ukraine 222669 1.8% 2.4%
OTHER 11.7% 15.0%

Contributing Subdomains

Domain Reach PageViews Per User
urbandecay.ru 98.43% 99.31% 3.5
OTHER 0 0.69% 0

Social Report


Hosting Info

urbandecay.ru Server Location
Server IP: 217.74.40.46
ASN: AS20919
ISP: IBS Expertise LLC
Server Location: Chekhov MOS 142300 Russia

Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Reputation / Confidence
Trustworthiness: 50 / 2
Child safety: 31 / 2
MyWOT Categories: N/A

Google PageSpeed Insights

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:
https://static.urbandecay.ru/media/css_secure/1ce018752d23b96354a5eba3334a89c4.css?t=201801110704

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://static.hotjar.com/c/hotjar-329828.js?sv=5 (60 seconds)
https://www.googletagmanager.com/gtm.js?id=GTM-5TF3MF (15 minutes)
https://connect.facebook.net/signals/config/1749334222010098?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/config/1894575380864125?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/config/335733360103340?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/config/505824676236626?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/iwl.js?v=2.8.6 (20 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://www.google-analytics.com/plugins/ua/ec.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://js-agent.newrelic.com/nr-1071.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

Reduce server response time

In our test, your server responded in 0.56 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 24.1KiB (27% reduction).
Compressing https://static.urbandecay.ru/skin/frontend/urbandecay/default/img/img-sign-for-news-2.jpg could save 24KiB (27% reduction).
Compressing https://static.urbandecay.ru/skin/frontend/urbandecay/default/img/icon_checkbox.png could save 120B (18% reduction).

Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 32% of the final above-the-fold content could be rendered with the full HTML response snapshot:2.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 645B (86% reduction).
Minifying https://connect.facebook.net/signals/plugins/iwl.js?v=2.8.6 could save 645B (86% reduction) after compression.

Enable compression

You have compression enabled. Learn more about enabling compression.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Optimize CSS Delivery of the following:
https://static.urbandecay.ru/media/css_secure/1ce018752d23b96354a5eba3334a89c4.css?t=201801110704

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://static.hotjar.com/c/hotjar-329828.js?sv=5 (60 seconds)
https://www.googletagmanager.com/gtm.js?id=GTM-5TF3MF (15 minutes)
https://connect.facebook.net/signals/config/1749334222010098?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/config/1894575380864125?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/config/335733360103340?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/config/505824676236626?v=2.8.6&r=stable (20 minutes)
https://connect.facebook.net/signals/plugins/iwl.js?v=2.8.6 (20 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://www.google-analytics.com/plugins/ua/ec.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://js-agent.newrelic.com/nr-1071.min.js (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)

Reduce server response time

In our test, your server responded in 0.54 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 416 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:
The element <button type="button" class="slick-next slick-arrow">Next</button> falls outside the viewport.

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 24.1KiB (27% reduction).
Compressing https://static.urbandecay.ru/skin/frontend/urbandecay/default/img/img-sign-for-news-2.jpg could save 24KiB (27% reduction).
Compressing https://static.urbandecay.ru/skin/frontend/urbandecay/default/img/icon_checkbox.png could save 120B (18% reduction).

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
The tap target <button type="button" class="slick-next slick-arrow">Next</button> is close to 2 other tap targets final.
The tap target <button type="button" class="slick-prev slick-arrow">Previous</button> is close to 2 other tap targets final.
The tap target <a href="https://urband…-lipstick.html" class="product-bundle…-product-click"></a> is close to 2 other tap targets final.
The tap target <button type="button" class="slick-next slick-arrow">Next</button> is close to 2 other tap targets final.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 645B (86% reduction).
Minifying https://connect.facebook.net/signals/plugins/iwl.js?v=2.8.6 could save 645B (86% reduction) after compression.

Avoid plugins

Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.

Configure the viewport

Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.

Enable compression

You have compression enabled. Learn more about enabling compression.

Minify HTML

Your HTML is minified. Learn more about minifying HTML.

Minify CSS

Your CSS is minified. Learn more about minifying CSS.

Use legible font sizes

The text on your page is legible. Learn more about using legible font sizes.

Prioritize visible content

You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.

Avoid landing page redirects

Your page has no redirects. Learn more about avoiding landing page redirects.

Http Header

Currently Not Available

DNS Lookup

Type Ip Target TTL
A 217.74.40.46 43198
NS ns3.nameshield.net 43198
NS ns2.observatoiredesmarques.fr 43198
NS obs.ns1.fr 43198
SOA 43200
MX mx.yandex.net 43200
TXT 43200

WhoIs Lookup

Domain Created: 2009-03-31
Domain Age: 10 years
WhoIs:
WhoIs lookup results from whois.tcinet.ru server:

domain:        URBANDECAY.RU
nserver:       ns2.observatoiredesmarques.fr.
nserver:       ns3.nameshield.net.
nserver:       obs.ns1.fr.
state:         REGISTERED, DELEGATED, VERIFIED
org:           L'OREAL SA
registrar:     RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created:       2009-03-31T20:00:00Z
paid-till:     2018-03-31T21:00:00Z
free-date:     2018-05-02
source:        TCI
Last updated on 2018-01-14T09