Show

D3.ru d3.ru – Популярное – Всё вместе

Need help with your SEO?
Online Status
Offline

Server IP address resolved: No
Http response code: None
Last Checked: 09/16/2019

D3.ru receives about ten thousand unique visitors and sixty thousand pageviews per day. The estimated value of d3.ru is one million USD. Each unique visitor makes about 4.13 pageviews on average.

Over the time d3.ru has been ranked as high as 4,043 in the world, while most of its traffic comes from Russian Federation, where it reached as high as 1,472 position.

It’s good for d3.ru that their server is also located in Russian Federation, as that enables the majority of their visitors to benefit from a much faster page load time.

At the time of the last check (July 04, 2019) d3.ru has a valid and up-to-date wildcard SSL certificate that expires on July 07, 2020.

According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust d3.ru is quite a safe domain.

Mobile-Friendly test indicates that d3.ru is well optimized for mobile and tablet devices, however website page loading time could be improved.

Global Rank
11,834
Average Load Time
1.29sec
Links In Count
596
Website Value
$989,880
Overview
Last Updated: 09/22/2019
Overall result - "d3.ru" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 11/01/2017
NCS "d3.ru" OK.

Norton ConnectSafe evaluates d3.ru for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 05/12/2017
GSS "d3.ru" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 01/09/2019
Malware not found at "d3.ru".
"d3.ru" is not a phishing page.
"d3.ru" does not install unwanted software.
"d3.ru" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 05/25/2017
SA "d3.ru" OK.

McAfee assesses d3.ru for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze d3.ru for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 01/12/2019
WOT "d3.ru" GOOD.

The WOT calculates reputation of the d3.ru. This reputation system receives ratings from users and information from third-party sources, assesses the d3.ru for safety features and confirms, whether d3.ru is suitable for children.

SSL Information
Domain *.d3.ru
Issuer Sectigo RSA Domain Validation Secure Server CA
Algorithm RSA-SHA256
Valid form 07/03/2019
Expiration 07/07/2020
Signed Certificate is not self signed
Additional Domains *.d3.ru
d3.ru
Server Location
Moscow
Moskva
Russian Federation
ASN Information

ASN ID: 197068
ASN Title: HLL LLC

Last Update: 05/30/2019

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to 'AS196608 - AS207259'

as-block: AS196608 - AS207259
descr: RIPE NCC ASN block
remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by: RIPE-NCC-HM-MNT
created: 2016-09-08T07:26:53Z
last-modified: 2016-09-08T07:26:53Z
source: RIPE

% Information related to 'AS197068'

% Abuse contact for 'AS197068' is 'abuse@qrator.net'

aut-num: AS197068
as-name: QRATOR
remarks: QRATOR filtering network
org: ORG-LA267-RIPE
import: from AS197068:AS-UPSTREAMS accept ANY
export: to AS197068:AS-UPSTREAMS announce AS-QRATOR
admin-c: QL-RIPE
tech-c: QL-RIPE
status: ASSIGNED
mnt-by: RIPE-NCC-END-MNT
mnt-by: MNT-QRATOR
mnt-routes: MNT-QRATOR
created: 2010-05-17T13:27:57Z
last-modified: 2016-04-14T08:50:27Z
source: RIPE

organisation: ORG-LA267-RIPE
org-name: HLL LLC
org-type: LIR
address: 1-y Magistralnyy tupik 5A,
Suite D/304
address: 123290
address: Moscow
address: RUSSIAN FEDERATION
phone: +74953746978
abuse-c: AR16870-RIPE
mnt-ref: RIPE-NCC-HM-MNT
mnt-ref: MNT-QRATOR
mnt-by: RIPE-NCC-HM-MNT
mnt-by: MNT-QRATOR
created: 2010-04-23T08:29:06Z
last-modified: 2017-05-12T11:43:50Z
source: RIPE # Filtered

role: Qrator Labs
address: 1-y Magistralnyy tupik 5A, Suite D/304
address: Moscow 123290
address: Russian Federation
org: ORG-LA267-RIPE
admin-c: LA27-RIPE
tech-c: AA8879-RIPE
tech-c: AZ2391-RIPE
nic-hdl: QL-RIPE
mnt-by: MNT-QRATOR
created: 2015-11-07T19:21:50Z
last-modified: 2017-05-12T11:54:26Z
source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.91.2 (ANGUS)

HTML Metatags
Title
d3.ru – Популярное – Всё вместе
The title has an optimal length. Search engines typically displays the first 50–70 characters of a title tag. If you keep your titles under 70 characters, our research suggests that you can expect about 90% of your titles to display properly.
Description
The description is too short. If a description is too short, the search engines may add text found elsewhere on the page. Note that search engines may show a different description from the one you have authored if they feel it may be more relevant to a user's search.
Encoding
UTF-8
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
Language not found
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
Not Found
Images
Attribute ALT
Line 154, ...<img style="display:none" hidden src="https://ad.adriver.ru/cgi-b...
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
The H1 tag is missing
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Add a header to the page by using a H1 tag and place it within the BODY of the page source.
H2
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
H5
H6
Iframes Information
iFrame
iFrames not found.
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
0.04 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (/robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
13 record(s)
Other User-Agent
Not found
Default User-Agent
1 record(s)
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File failed Loaded (/sitemap.xml)
Your site will benefit from having a sitemap.
WHOIS

% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: D3.RU
nserver: ns3-l2.nic.ru.
nserver: ns4-cloud.nic.ru.
nserver: ns4-l2.nic.ru.
nserver: ns8-cloud.nic.ru.
nserver: ns8-l2.nic.ru.
state: REGISTERED, DELEGATED, VERIFIED
org: Futuware Limited
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 2000-12-03T21:00:00Z
paid-till: 2018-12-05T21:00:00Z
free-date: 2019-01-06
source: TCI

Last updated on 2018-11-08T13:16:31Z

DNS Records
HostA RecordTTL
d3.ru178.248.237.157200
HostMX RecordPriorityTTL
d3.rualt1.aspmx.l.google.com57200
d3.ruaspmx3.googlemail.com107200
d3.rualt2.aspmx.l.google.com57200
d3.ruaspmx2.googlemail.com107200
d3.ruaspmx.l.google.com17200
HostNS RecordTTL
d3.runs3-l2.nic.ru3600
d3.runs8-cloud.nic.ru3600
d3.runs4-l2.nic.ru3600
d3.runs4-cloud.nic.ru3600
d3.runs8-l2.nic.ru3600
HostTXT RecordTTL
d3.rumailru-verification: a47e57703912e5517200
d3.ruyandex-verification: 12b0a3d2b9c185167200
d3.ruv=spf1 ip4:5.9.218.171 a mx include:aspmx.googlemail.com include:spf.mandrillapp.com ~all7200

ns3-l2.nic.ru
TTL: 7200
Email address: dns.nic.ru
Serial: 2018052111
Refresh: 900
Retry: 900
Expire: 3024000
Minimum: 900

Warnings
Line: 48 Column: 9 - 39
"... <script type="text/javascript"> (func..."
Errors
Line: 161 Column: 5 - 11
"... </head> <..."
Line: 162 Column: 5 - 84
"...head> <body itemscope itemtype="http://schema.org/WebPage" style="overflow-y: scroll"> ..."
Line: 162 Column: 5 - 84
"...head> <body itemscope itemtype="http://schema.org/WebPage" style="overflow-y: scroll"> ..."

Last tested: 02/07/2018

Desktop
Desktop Speed
72%
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://cdn.jpg.wtf/futurico/31/7c/1416406961-317c…6d864b154c408a6b12.png (expiration not specified)
https://cdn.jpg.wtf/futurico/4E/3B/34637-4cad840b6…e0b40eb23eee3071fb.png (expiration not specified)
https://cdn.jpg.wtf/futurico/5E/D3/24754-e2d6f80c2…8aebf3a258a2d4fafe.png (expiration not specified)
https://cdn.jpg.wtf/futurico/61/f4/1517963171-61f4…40dbe38844c23914ab.png (expiration not specified)
https://cdn.jpg.wtf/futurico/75/F0/29568-387458134…236f0f0c2dede0511d.png (expiration not specified)
https://cdn.jpg.wtf/futurico/81/a5/1460894810-81a5…86e4006cda0b2849e.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/91/EC/26180-2c1825287…35970ec81a2a366814.png (expiration not specified)
https://cdn.jpg.wtf/futurico/AB/8D/31474-fc0ca458f…e08070ec3577a8f263.png (expiration not specified)
https://cdn.jpg.wtf/futurico/C2/83/31474-1c9ac553c…2d0f649abd8f9e090d.png (expiration not specified)
https://cdn.jpg.wtf/futurico/c8/cb/1434013796-c8cb…4438ee4f7dabbc1f9d.png (expiration not specified)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://an.yandex.ru/system/context.js (60 minutes)
https://content.adriver.ru/banners/0002186/0002186173/0/AV.js (60 minutes)
https://content.adriver.ru/banners/0002186/0002186173/0/a6.js (60 minutes)
https://content.adriver.ru/plugins/min/autoUpdate.adriver.js (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://servers5.adriver.ru/images/0001062/0001062…0/script.js?vb-promo-2 (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://yastatic.net/pcode/media/loader.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 90.1KiB (66% reduction).

Compressing https://yastatic.net/q/set/s/rsya-tag-users/bundle.js could save 67.7KiB (67% reduction).
Compressing https://content.adriver.ru/banners/0002186/0002186173/0/AV.js could save 9.6KiB (71% reduction).
Compressing https://content.adriver.ru/banners/0002186/0002186173/0/a6.js could save 9KiB (64% reduction).
Compressing https://content.adriver.ru/plugins/min/autoUpdate.adriver.js could save 1.8KiB (55% reduction).
Compressing https://ad.adriver.ru/cgi-bin/merle.cgi?rnd=541450…t=52&sz=/&ph=b-promo-2 could save 1.4KiB (52% reduction).
Compressing https://content.adriver.ru/banners/0002186/0002186…65&66.102.8.47&merle&1 could save 594B (45% reduction).

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 79.3KiB (41% reduction).

Compressing https://avatars.mds.yandex.net/get-direct-picture/…qs-9U74WKcCZy3IpA/orig could save 59.6KiB (50% reduction).
Compressing https://cdn.jpg.wtf/futurico/81/a5/1460894810-81a5…86e4006cda0b2849e.jpeg could save 6.9KiB (37% reduction).
Compressing https://cdn.jpg.wtf/futurico/4E/3B/34637-4cad840b6…e0b40eb23eee3071fb.png could save 3.5KiB (34% reduction).
Compressing https://cdn.jpg.wtf/futurico/5E/D3/24754-e2d6f80c2…8aebf3a258a2d4fafe.png could save 2.5KiB (37% reduction).
Compressing https://cdn.jpg.wtf/futurico/75/F0/29568-387458134…236f0f0c2dede0511d.png could save 2.5KiB (15% reduction).
Compressing https://cdn.jpg.wtf/futurico/c8/cb/1434013796-c8cb…4438ee4f7dabbc1f9d.png could save 1.5KiB (27% reduction).
Compressing https://d3.ru/static/i/logo_main_beta.png could save 1.1KiB (13% reduction).
Compressing https://d3.ru/static/i/logo_main_retina.png could save 1KiB (13% reduction).
Compressing https://d3.ru/static/i/logo_retina.png could save 625B (25% reduction).

Your page has 3 blocking script 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.Remove render-blocking JavaScript:

https://d3.ru/static/cache/loader_27eede9800f47e51b100:ru.js
https://d3.ru/static/js/adriver.core.2.min.js
https://cdn.ravenjs.com/3.12.0/raven.min.js

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.

None of the final above-the-fold content could be rendered even with the full HTML response.

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 2.2KiB (14% reduction).

Minifying https://content.adriver.ru/banners/0002186/0002186173/0/a6.js could save 1.9KiB (14% reduction).
Minifying https://ad.adriver.ru/cgi-bin/merle.cgi?rnd=541450…t=52&sz=/&ph=b-promo-2 could save 321B (13% reduction).

In our test, your server responded in 0.22 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.
Desktop Resource Breakdown
Total Resources152
Number of Hosts34
Static Resources51
JavaScript Resources39
CSS Resources2

Last tested: 06/14/2019

Mobile
Mobile Usability
99%
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 <a id="b-link-117" href="https://d3.ru/…iiane-1801002/" class="b-link b-link_…st-title__link">Сбербанк узнае…дятся россияне</a> is close to 1 other tap targets.
The tap target <yatag class="f235e67da wf26…309b ud100c81a">Скрыть объявление</yatag> is close to 1 other tap targets.
The tap target <div class="b-rating__value"></div> and 7 others are close to other tap targets.
The tap target <a href="javascript: void 0" class="b-action b-act…n__auth-action">Зарегистрируйтесь</a> and 1 others are close to other tap targets.
The tap target <div class="b-select__option">Любой</div> and 1 others are close to other tap targets final.

Mobile Speed
15%
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 3.4MiB (59% reduction).

Compressing https://cdn.jpg.wtf/futurico/1a/cf/1470671478-1acf…416d99f9d510dd0e5.jpeg could save 3.2MiB (61% reduction).
Compressing https://cdn.jpg.wtf/futurico/1a/c4/1495093721-1ac4…03d14ffea82121831.jpeg could save 187.2KiB (47% reduction).
Compressing https://cdn.jpg.wtf/futurico/d0/7f/1560269756-d07f…044479711dccb387f.jpeg could save 16KiB (72% reduction).
Compressing https://cdn.jpg.wtf/futurico/db/96/1449803245-db96…110d410b7fdb6dc51.jpeg could save 9KiB (64% reduction).
Compressing https://cdn.jpg.wtf/futurico/a3/66/1560511300-a366…7b123bfbd799bd891.jpeg could save 6.6KiB (20% reduction).
Compressing https://cdn.jpg.wtf/futurico/b6/b2/1560495063-b6b2…7a0b3dc199d.jpeg?w=700 could save 4.8KiB (12% reduction).
Compressing https://cdn.jpg.wtf/futurico/3a/f7/1517814415-3af7…3e8cdb771da68648b.jpeg could save 3.8KiB (41% reduction).
Compressing https://cdn.jpg.wtf/futurico/4E/3B/34637-4cad840b6…e0b40eb23eee3071fb.png could save 3.5KiB (34% reduction).
Compressing https://cdn.jpg.wtf/futurico/c8/cb/1434013796-c8cb…4438ee4f7dabbc1f9d.png could save 1.5KiB (27% reduction).
Compressing https://d3.ru/static/i/logo_main_beta.png could save 1.1KiB (13% reduction).
Compressing https://d3.ru/static/i/logo_main_retina.png could save 1KiB (13% reduction).
Compressing https://cdn.jpg.wtf/futurico/b6/10/1445499509-b610…e3c07a0a9c6e1d6365.png could save 899B (15% reduction).
Compressing https://cdn.jpg.wtf/futurico/b9/a9/1424471301-b9a9…d4eaa1150943d4bf5f.gif could save 264B (12% reduction).

Your page has 3 blocking script 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.Remove render-blocking JavaScript:

https://d3.ru/static/cache/loader_27eede9800f47e51b100:ru.js
https://d3.ru/static/js/adriver.core.2.min.js
https://cdn.ravenjs.com/3.12.0/raven.min.js

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://cdn.jpg.wtf/futurico/00/8d/1435762306-008d…5426599c0a402d303f.png (expiration not specified)
https://cdn.jpg.wtf/futurico/1a/c4/1495093721-1ac4…03d14ffea82121831.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/1a/cf/1470671478-1acf…416d99f9d510dd0e5.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/2e/68/1550470057-2e68…4fd08e62b91ec5559.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/3a/04/1366889926-3a04…d4bb86e805ed7463d0.png (expiration not specified)
https://cdn.jpg.wtf/futurico/3a/f7/1517814415-3af7…3e8cdb771da68648b.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/4E/3B/34637-4cad840b6…e0b40eb23eee3071fb.png (expiration not specified)
https://cdn.jpg.wtf/futurico/AC/BE/14376-1c996f1f6…c6e05995b242efa08a.png (expiration not specified)
https://cdn.jpg.wtf/futurico/a3/66/1560511300-a366…7b123bfbd799bd891.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/b6/10/1445499509-b610…e3c07a0a9c6e1d6365.png (expiration not specified)
https://cdn.jpg.wtf/futurico/b9/a9/1424471301-b9a9…d4eaa1150943d4bf5f.gif (expiration not specified)
https://cdn.jpg.wtf/futurico/c8/cb/1434013796-c8cb…4438ee4f7dabbc1f9d.png (expiration not specified)
https://cdn.jpg.wtf/futurico/c9/12/1560497841-c912…12478ad6aafa261ec7.png (expiration not specified)
https://cdn.jpg.wtf/futurico/d0/7f/1560269756-d07f…044479711dccb387f.jpeg (expiration not specified)
https://cdn.jpg.wtf/futurico/db/96/1449803245-db96…110d410b7fdb6dc51.jpeg (expiration not specified)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://an.yandex.ru/system/context.js (60 minutes)
https://content.adriver.ru/plugins/min/autoUpdate.adriver.js (60 minutes)
https://mc.yandex.ru/metrika/advert.gif (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

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.

None of the final above-the-fold content could be rendered even with the full HTML response.

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 1.9KiB (52% reduction).

Compressing https://content.adriver.ru/plugins/min/autoUpdate.adriver.js could save 1.8KiB (55% reduction).
Compressing https://yandex.ru/set/s/rsya-tag-users/data?_rnd=1…https%3A%2F%2Fd3.ru%2F could save 139B (35% reduction).

Mobile Resource Breakdown
Total Resources125
Number of Hosts31
Static Resources46
JavaScript Resources34
CSS Resources2
www.d3.com
www.d3.net
www.d3.org
www.d3.info
www.d3.biz
www.d3.us
www.d3.mobi
www.3.ru
www.d3.ru
www.x3.ru
www.dx3.ru
www.xd3.ru
www.s3.ru
www.ds3.ru
www.sd3.ru
www.e3.ru
www.de3.ru
www.ed3.ru
www.r3.ru
www.dr3.ru
www.rd3.ru
www.f3.ru
www.df3.ru
www.fd3.ru
www.c3.ru
www.dc3.ru
www.cd3.ru
www.d.ru