peopletalk.ru

peopletalk.ru is SSL secured

Free website and domain report on peopletalk.ru

Last Updated: 15th August, 2020 Update Now
Overview

Snoop Summary for peopletalk.ru

This is a free and comprehensive report about peopletalk.ru. The domain peopletalk.ru is currently hosted on a server located in Germany with the IP address 195.201.175.82, where EUR is the local currency and the local language is German. Peopletalk.ru is expected to earn an estimated $135 USD per day from advertising revenue. The sale of peopletalk.ru would possibly be worth $98,448 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Peopletalk.ru receives an estimated 31,887 unique visitors every day - a massive amount of traffic! This report was last updated 15th August, 2020.

About peopletalk.ru

Site Preview: peopletalk.ru peopletalk.ru
Title: Новости шоу-бизнеса. Последние новости о звездах шоу-бизнеса на сайте PEOPLETALK
Description: На PEOPLETALK вы найдете самые актуальные новости о звездах шоу-бизнеса на сегодня. Только свежие новости, фотографии, а так же горячие сплетни и слухи о звездах России и Голливуда.
Keywords and Tags: entertainment
Related Terms:
Fav Icon:
Age: Over 16 years old
Domain Created: 31st May, 2007
Domain Updated:
Domain Expires: 31st May, 2021
Review

Snoop Score

4/5 (Excellent!)

Valuation

$98,448 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 24,117
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 31,887
Monthly Visitors: 970,540
Yearly Visitors: 11,638,755
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $135 USD
Monthly Revenue: $4,104 USD
Yearly Revenue: $49,219 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: peopletalk.ru 13
Domain Name: peopletalk 10
Extension (TLD): ru 2
Expiry Check:

Page Speed Analysis

Average Load Time: 2.08 seconds
Load Time Comparison: Faster than 42% of sites

PageSpeed Insights

Avg. (All Categories) 77
Performance 94
Accessibility 74
Best Practices 69
SEO 100
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://peopletalk.ru/
Updated: 15th August, 2020

1.10 seconds
First Contentful Paint (FCP)
71%
24%
5%

0.00 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on desktop
94

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for peopletalk.ru. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.1 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.004
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive peopletalk.ru as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://peopletalk.ru/
0
222.88699983619
145
0
301
https://peopletalk.ru/
223.21800002828
806.26500002109
61648
553860
200
text/html
Document
https://peopletalk.ru/wp-content/cache/minify/a5ff7.css?v=3.0.1
829.13399999961
937.4700000044
7917
41467
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Montserrat%3A400%2C500%7COswald&display=swap&subset=cyrillic&ver=1.0.0
829.58299992606
845.71000002325
1765
5840
200
text/css
Stylesheet
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
829.93500004523
1386.6309998557
53262
267266
200
text/css
Stylesheet
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
847.16699994169
1477.7879999019
193760
546335
200
application/javascript
Script
1410.2039998397
1410.4279999156
0
11802
200
image/jpeg
Image
1410.7500000391
1410.8080000151
0
1307
200
image/jpeg
Image
1411.1760000233
1411.2849999219
0
4718
200
image/jpeg
Image
1411.482000025
1411.5199998487
0
722
200
image/jpeg
Image
https://fonts.gstatic.com/s/oswald/v35/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUJiYySUhiCXABTV.woff
1426.4759998769
1429.7449998558
7740
7148
200
font/woff
Font
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_ZpC3g3D_vx3rCubqg.woff2
1428.2869999297
1431.2680000439
8721
8128
200
font/woff2
Font
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/fonts/icomoon.ttf?4kvre7
1429.644000018
1537.1270000469
5536
5208
200
application/octet-stream
Font
https://fonts.gstatic.com/s/oswald/v35/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYySUhiCXAA.woff
1430.2669998724
1433.2850000355
13265
12672
200
font/woff
Font
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
1430.6459999643
1433.6500000209
14234
13640
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
1432.0729998872
1434.5199998934
14302
13708
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459W1hyyTh89ZNpQ.woff2
1453.2859998289
1456.5709999297
8701
8108
200
font/woff2
Font
1483.4469999187
1483.5009998642
0
1922
200
image/jpeg
Image
1554.186000023
1554.3219998945
0
8200
200
image/jpeg
Image
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/img/icons/other/16+.svg
1561.9029998779
1875.7219999097
1572
2683
200
image/svg+xml
Image
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/assets/img/ajax-loader.gif
1769.0569998231
1909.4229999464
4506
4178
200
image/gif
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-8.jpg?opt=true
1927.5409998372
2239.8850000463
63796
63528
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-10.jpg?opt=true
1927.801999962
2138.3479998913
70481
70212
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/sasha-morozova.jpg?opt=true
1928.0159999616
2445.7099998835
75203
74934
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-9.jpg?opt=true
1928.251999896
2344.4919998292
34566
34298
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-11.jpg?opt=true
1928.3829999622
2345.02899996
22336
22068
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/06/luga.jpg?opt=true
1928.8229998201
2453.3629999496
88607
88338
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/117406444_4256988044372125_6006411030032497285_n-560x470.jpg?opt=true
1928.9869999047
2451.4699999709
42832
42564
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/whatsapp-image-2020-08-14-at-15.46.38888-560x470.jpeg?opt=true
1929.3579999357
2463.1539999973
48362
48094
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
1929.730999982
3089.6689998917
3818967
3818634
200
image/gif
Image
https://peopletalk.ru/wp-content/uploads/2020/06/101660104_177730320302627_6687439950019281647_n-560x470.jpg?opt=true
1929.9820000306
2454.1390000377
64280
64012
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/07/ty-560x470.jpg?opt=true
1930.1030000206
2038.4919999633
21152
20884
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2017/01/angelina-jolie-5470666b-5569-442a-ae92-46ad947085c4-e1583767929111-560x470.jpg?opt=true
1930.3829998244
2454.9340000376
50082
49814
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2019/07/billie-eilish-getty-steve-jennings-560x470.jpg?opt=true
1931.1329999473
2350.9700000286
32992
32724
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/03/2cabaaa7-a9a7-417a-9b53-a35c78a63955-560x470.jpeg?opt=true
1933.6889998522
2350.2439998556
36386
36118
200
image/webp
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
840.395
14.887
1418.601
9.408
1428.057
15.235
1443.315
53.182
1514.448
59.424
1577.383
8.02
1586.068
27.491
1615.224
58.813
1675.833
18.611
1694.778
6.927
1702.534
5.98
1718.129
68.894
1787.224
64.368
1853.037
13.818
1940.615
21.39
2070.642
8.752
2170.73
6.334
2272.199
5.776
2477.961
5.925
2495.79
5.649
2503.255
5.028
2516.775
5.206
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 40 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Peopletalk.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://peopletalk.ru/wp-content/cache/minify/a5ff7.css?v=3.0.1
7917
110
https://fonts.googleapis.com/css?family=Montserrat%3A400%2C500%7COswald&display=swap&subset=cyrillic&ver=1.0.0
1765
230
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
53262
390
Properly size images
Images can slow down the page's load time. Peopletalk.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Peopletalk.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Peopletalk.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Peopletalk.ru should consider minifying JS files.
Remove unused CSS — Potential savings of 45 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Peopletalk.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
53262
46541
Remove unused JavaScript — Potential savings of 139 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
193760
142033
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 580 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Peopletalk.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://peopletalk.ru/
0
https://peopletalk.ru/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Peopletalk.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Diagnostics

Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Peopletalk.ru should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://peopletalk.ru/
313.565
21.5
5.06
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
291.953
205.986
9.732
Unattributable
75.187
1.65
0.272
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
229.536
Script Evaluation
229.136
Other
121.801
Rendering
68.71
Parse HTML & CSS
29.298
Script Parsing & Compilation
15.064
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 29 requests • 4,753 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
29
4867116
Image
16
4476120
Script
1
193760
Font
7
72499
Stylesheet
3
62944
Document
1
61648
Other
1
145
Media
0
0
Third-party
7
68728
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
68728
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
1070
59

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 1.6 s
The time taken for the page contents to be visibly populated.

Opportunities

Use video formats for animated content — Potential savings of 3,394 KiB
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
3818634
3474957

Diagnostics

Avoid enormous network payloads — Total size was 4,753 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
3818967
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
193760
https://peopletalk.ru/wp-content/uploads/2020/06/luga.jpg?opt=true
88607
https://peopletalk.ru/wp-content/uploads/2020/08/sasha-morozova.jpg?opt=true
75203
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-10.jpg?opt=true
70481
https://peopletalk.ru/wp-content/uploads/2020/06/101660104_177730320302627_6687439950019281647_n-560x470.jpg?opt=true
64280
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-8.jpg?opt=true
63796
https://peopletalk.ru/
61648
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
53262
https://peopletalk.ru/wp-content/uploads/2017/01/angelina-jolie-5470666b-5569-442a-ae92-46ad947085c4-e1583767929111-560x470.jpg?opt=true
50082
Serve static assets with an efficient cache policy — 20 resources found
Peopletalk.ru can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
2592000000
3818967
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
2592000000
193760
https://peopletalk.ru/wp-content/uploads/2020/06/luga.jpg?opt=true
2592000000
88607
https://peopletalk.ru/wp-content/uploads/2020/08/sasha-morozova.jpg?opt=true
2592000000
75203
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-10.jpg?opt=true
2592000000
70481
https://peopletalk.ru/wp-content/uploads/2020/06/101660104_177730320302627_6687439950019281647_n-560x470.jpg?opt=true
2592000000
64280
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-8.jpg?opt=true
2592000000
63796
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
2592000000
53262
https://peopletalk.ru/wp-content/uploads/2017/01/angelina-jolie-5470666b-5569-442a-ae92-46ad947085c4-e1583767929111-560x470.jpg?opt=true
2592000000
50082
https://peopletalk.ru/wp-content/uploads/2020/08/whatsapp-image-2020-08-14-at-15.46.38888-560x470.jpeg?opt=true
2592000000
48362
https://peopletalk.ru/wp-content/uploads/2020/08/117406444_4256988044372125_6006411030032497285_n-560x470.jpg?opt=true
2592000000
42832
https://peopletalk.ru/wp-content/uploads/2020/03/2cabaaa7-a9a7-417a-9b53-a35c78a63955-560x470.jpeg?opt=true
2592000000
36386
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-9.jpg?opt=true
2592000000
34566
https://peopletalk.ru/wp-content/uploads/2019/07/billie-eilish-getty-steve-jennings-560x470.jpg?opt=true
2592000000
32992
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-11.jpg?opt=true
2592000000
22336
https://peopletalk.ru/wp-content/uploads/2020/07/ty-560x470.jpg?opt=true
2592000000
21152
https://peopletalk.ru/wp-content/cache/minify/a5ff7.css?v=3.0.1
2592000000
7917
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/fonts/icomoon.ttf?4kvre7
2592000000
5536
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/assets/img/ajax-loader.gif
2592000000
4506
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/img/icons/other/16+.svg
2592000000
1572
Avoid an excessive DOM size — 1,637 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1,637
Maximum DOM Depth
14
Maximum Child Elements
27
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
line: 0
74

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of peopletalk.ru. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Peopletalk.ru may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Peopletalk.ru may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
69

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that peopletalk.ru should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.3.1
jQuery
3.2.1
Mustache
3.1.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://peopletalk.ru/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://peopletalk.ru/
ReferenceError: fbq is not defined at https://peopletalk.ru/:115:3
https://peopletalk.ru/
ReferenceError: fbq is not defined at https://peopletalk.ru/:119:3
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for peopletalk.ru. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of peopletalk.ru on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
48

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of peopletalk.ru. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of peopletalk.ru on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://peopletalk.ru/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 72
Performance 71
Accessibility 74
Best Practices 69
SEO 96
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://peopletalk.ru/
Updated: 15th August, 2020

1.16 seconds
First Contentful Paint (FCP)
68%
27%
5%

0.04 seconds
First Input Delay (FID)
90%
8%
2%

Simulate loading on mobile
71

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for peopletalk.ru. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Estimated Input Latency — 30 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive peopletalk.ru as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://peopletalk.ru/
0
105.24199996144
133
0
301
https://peopletalk.ru/
105.62699998263
430.94500002917
61648
553860
200
text/html
Document
https://peopletalk.ru/wp-content/cache/minify/a5ff7.css?v=3.0.1
448.67800001521
559.24700002652
7917
41467
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Montserrat%3A400%2C500%7COswald&display=swap&subset=cyrillic&ver=1.0.0
448.79200006835
466.8890000321
1670
5839
200
text/css
Stylesheet
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
449.1670000134
771.59300004132
53262
267266
200
text/css
Stylesheet
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
467.45100000408
889.1280000098
193760
546335
200
application/javascript
Script
796.51000001468
796.69900005683
0
11802
200
image/jpeg
Image
796.99100006837
797.03999997582
0
1307
200
image/jpeg
Image
797.37000004388
797.44600004051
0
4718
200
image/jpeg
Image
797.60300007183
797.63100005221
0
722
200
image/jpeg
Image
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/fonts/icomoon.ttf?4kvre7
811.61700002849
916.59599996638
5536
5208
200
application/octet-stream
Font
https://fonts.gstatic.com/s/oswald/v35/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUJiZSSShiC_AA.woff2
812.77099996805
815.8420000691
6145
5552
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_ZpC3g3D_vx3rCubqg.woff2
814.54200006556
817.65500002075
8721
8128
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v14/JTURjIg1_i6t8kCHKm45_ZpC3gnD_vx3rCs.woff2
815.72499999311
818.58399999328
14234
13640
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2
816.99500000104
819.6229999885
14302
13708
200
font/woff2
Font
https://fonts.gstatic.com/s/oswald/v35/TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiZSSShiA.woff2
818.47599998582
821.39100006316
10365
9772
200
font/woff2
Font
https://fonts.gstatic.com/s/montserrat/v14/JTUSjIg1_i6t8kCHKm459W1hyyTh89ZNpQ.woff2
831.37600007467
834.02599999681
8701
8108
200
font/woff2
Font
899.36899999157
899.42200004589
0
1922
200
image/jpeg
Image
933.86800005101
934.00900007691
0
8200
200
image/jpeg
Image
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/img/icons/other/16+.svg
941.087000072
1047.2180000506
1572
2683
200
image/svg+xml
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-8.jpg?opt=true
1149.1490000626
1256.5950000426
63796
63528
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-10.jpg?opt=true
1149.2820000276
1257.3270000285
70481
70212
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/sasha-morozova.jpg?opt=true
1149.6390000684
1461.6140000289
75203
74934
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-9.jpg?opt=true
1150.277000037
1358.7919999845
34566
34298
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-11.jpg?opt=true
1150.5340000149
1359.3259999761
22336
22068
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/06/luga.jpg?opt=true
1150.6700000027
1463.1330000702
88607
88338
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
1150.8760000579
2094.5310000097
3818967
3818634
200
image/gif
Image
https://peopletalk.ru/wp-content/uploads/2020/06/101660104_177730320302627_6687439950019281647_n-560x470.jpg?opt=true
1151.1099999771
1464.3739999738
64280
64012
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/07/ty-560x470.jpg?opt=true
1151.2319999747
1568.5560000129
21152
20884
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2017/01/angelina-jolie-5470666b-5569-442a-ae92-46ad947085c4-e1583767929111-560x470.jpg?opt=true
1151.4360000147
1467.5670000724
50082
49814
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2019/07/billie-eilish-getty-steve-jennings-560x470.jpg?opt=true
1152.7580000693
1570.2479999745
32992
32724
200
image/webp
Image
https://peopletalk.ru/wp-content/uploads/2020/03/2cabaaa7-a9a7-417a-9b53-a35c78a63955-560x470.jpeg?opt=true
1155.7950000279
1363.9119999716
36386
36118
200
image/webp
Image
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/assets/img/ajax-loader.gif
1186.417000019
1291.7440000456
4506
4178
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
467.492
9.89
806.433
10.717
817.204
14.614
831.836
47.528
892.684
35.125
934.765
25.814
961.058
6.54
968.207
28.99
997.622
58.351
1057.379
14.819
1072.977
6.986
1080.778
5.445
1093.699
64.207
1159.835
25.474
1186.787
14.566
1203.712
50.384
1254.633
11.739
1290.156
5.656
1297.138
6.123
1316.103
5.273
1405.774
5.13
1500.045
5.24
2148.676
14.875
2163.573
5.851
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Peopletalk.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Peopletalk.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Peopletalk.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Peopletalk.ru should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 330 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Peopletalk.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://peopletalk.ru/
0
https://peopletalk.ru/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Peopletalk.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Diagnostics

Avoid chaining critical requests — 11 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Peopletalk.ru should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
1308.104
826.54
34.46
https://peopletalk.ru/
984.784
76.688
21.26
Unattributable
326.112
5.336
0.716
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 27 requests • 4,659 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
27
4771320
Image
14
4384926
Script
1
193760
Font
7
68004
Stylesheet
3
62849
Document
1
61648
Other
1
133
Media
0
0
Third-party
7
64138
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
64138
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 12 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
4350
233
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
4666
128
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
4849
101
https://peopletalk.ru/
1476
95
https://peopletalk.ru/
1571
70
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
4950
60
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
4585
59
https://peopletalk.ru/
1418
58
https://peopletalk.ru/
1693
58
https://peopletalk.ru/
630
58
https://peopletalk.ru/
1641
52
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
4798
51

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 3.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 4.0 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 4.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 300 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 4.7 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 230 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.0 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 300 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Peopletalk.ru should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://peopletalk.ru/wp-content/cache/minify/a5ff7.css?v=3.0.1
7917
330
https://fonts.googleapis.com/css?family=Montserrat%3A400%2C500%7COswald&display=swap&subset=cyrillic&ver=1.0.0
1670
780
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
53262
1230
Remove unused CSS — Potential savings of 45 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Peopletalk.ru should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
53262
46057
Remove unused JavaScript — Potential savings of 139 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
193760
141977

Diagnostics

Minimize main-thread work — 2.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
908.56399999999
Style & Layout
772.488
Other
499.008
Rendering
290.16
Parse HTML & CSS
149.236
Script Parsing & Compilation
56.436

Metrics

Largest Contentful Paint — 4.7 s
The timing of the largest text or image that is painted.

Opportunities

Use video formats for animated content — Potential savings of 3,394 KiB
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
3818634
3474957

Diagnostics

Avoid enormous network payloads — Total size was 4,659 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
3818967
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
193760
https://peopletalk.ru/wp-content/uploads/2020/06/luga.jpg?opt=true
88607
https://peopletalk.ru/wp-content/uploads/2020/08/sasha-morozova.jpg?opt=true
75203
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-10.jpg?opt=true
70481
https://peopletalk.ru/wp-content/uploads/2020/06/101660104_177730320302627_6687439950019281647_n-560x470.jpg?opt=true
64280
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-8.jpg?opt=true
63796
https://peopletalk.ru/
61648
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
53262
https://peopletalk.ru/wp-content/uploads/2017/01/angelina-jolie-5470666b-5569-442a-ae92-46ad947085c4-e1583767929111-560x470.jpg?opt=true
50082
Serve static assets with an efficient cache policy — 18 resources found
Peopletalk.ru can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://peopletalk.ru/wp-content/uploads/2019/01/p_texting_2.gif?opt=true
2592000000
3818967
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
2592000000
193760
https://peopletalk.ru/wp-content/uploads/2020/06/luga.jpg?opt=true
2592000000
88607
https://peopletalk.ru/wp-content/uploads/2020/08/sasha-morozova.jpg?opt=true
2592000000
75203
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-10.jpg?opt=true
2592000000
70481
https://peopletalk.ru/wp-content/uploads/2020/06/101660104_177730320302627_6687439950019281647_n-560x470.jpg?opt=true
2592000000
64280
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-8.jpg?opt=true
2592000000
63796
https://peopletalk.ru/wp-content/cache/minify/fcac3.css?v=3.0.1
2592000000
53262
https://peopletalk.ru/wp-content/uploads/2017/01/angelina-jolie-5470666b-5569-442a-ae92-46ad947085c4-e1583767929111-560x470.jpg?opt=true
2592000000
50082
https://peopletalk.ru/wp-content/uploads/2020/03/2cabaaa7-a9a7-417a-9b53-a35c78a63955-560x470.jpeg?opt=true
2592000000
36386
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-9.jpg?opt=true
2592000000
34566
https://peopletalk.ru/wp-content/uploads/2019/07/billie-eilish-getty-steve-jennings-560x470.jpg?opt=true
2592000000
32992
https://peopletalk.ru/wp-content/uploads/2020/08/bez-imeni-1-11.jpg?opt=true
2592000000
22336
https://peopletalk.ru/wp-content/uploads/2020/07/ty-560x470.jpg?opt=true
2592000000
21152
https://peopletalk.ru/wp-content/cache/minify/a5ff7.css?v=3.0.1
2592000000
7917
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/fonts/icomoon.ttf?4kvre7
2592000000
5536
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/assets/img/ajax-loader.gif
2592000000
4506
https://peopletalk.ru/wp-content/themes/peopletalk2019/dist/img/icons/other/16+.svg
2592000000
1572
Avoid an excessive DOM size — 1,637 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1,637
Maximum DOM Depth
14
Maximum Child Elements
27
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://peopletalk.ru/wp-content/cache/minify/146e9.js?v=3.0.1
line: 0

Other

First Contentful Paint (3G) — 6120 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
74

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of peopletalk.ru. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Names and labels

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Peopletalk.ru may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Peopletalk.ru may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons do not have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Contrast

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
69

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that peopletalk.ru should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.3.1
jQuery
3.2.1
Mustache
3.1.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://peopletalk.ru/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 3 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
3
Medium

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://peopletalk.ru/
ReferenceError: fbq is not defined at https://peopletalk.ru/:115:3
https://peopletalk.ru/
ReferenceError: fbq is not defined at https://peopletalk.ru/:119:3
96

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for peopletalk.ru. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of peopletalk.ru on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 58% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
40x40
img
41x15
41x15
44x15
44x15
47x15
47x15
85x15
110x15
86x15
86x15
89x15
104x15
89x15
65x15
89x15
110x15
89x15
70x15
86x15
70x15
86x15
70x15
50x15
70x15
62x15
61x15
125x15
58x15
122x15
77x15
70x15
121x15
51x15
75x15
61x15
128x15
58x15
197x15
62x15
121x15
65x15
146x15
65x15
197x15
85x16
90x16
86x16
86x16
89x16
70x18
72x18
66x18
102x15
55x15
a
20x24
a
a
20x24
a
a
20x24
a
a
20x24
a
a
20x24
a
a
20x24
a
a
20x24
a

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of peopletalk.ru. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of peopletalk.ru on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://peopletalk.ru/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 195.201.175.82
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 3.1/5 (3 reviews)
WOT Trustworthiness: 62/100
WOT Child Safety: 99/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: s1.peopletalk.ru
Issued By: Let's Encrypt Authority X3
Valid From: 22nd June, 2020
Valid To: 20th September, 2020
Subject: CN = s1.peopletalk.ru
Hash: 4cb96d03
Issuer: CN = Let's Encrypt Authority X3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03578E239E7D49D536C044640E3876E60EB4
Serial Number (Hex): 03578E239E7D49D536C044640E3876E60EB4
Valid From: 22nd June, 2024
Valid To: 20th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://ocsp.int-x3.letsencrypt.org
CA Issuers - URI:http://cert.int-x3.letsencrypt.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
Timestamp : Jun 22 14:53:59.976 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:3B:93:22:6A:A5:91:96:78:14:C1:91:79:
CE:12:D5:89:CA:38:71:BE:89:DD:9A:73:58:71:CF:A3:
CD:0D:E1:99:02:21:00:E4:FC:F3:90:23:CA:FF:EA:05:
FE:EE:92:29:9E:E7:DA:B0:5F:93:89:32:E1:FA:04:D4:
92:40:3A:C4:C4:48:E3
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
Timestamp : Jun 22 14:54:00.021 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:55:44:1A:C0:D0:2D:E0:62:9C:B4:EA:3A:
72:F7:AB:9F:E5:24:73:B6:E0:4B:D5:B5:0A:5B:82:74:
4E:FD:CC:E2:02:20:5A:84:39:3E:7A:34:E3:07:8A:B5:
AA:1B:63:FC:73:F0:32:6D:0C:E0:CB:57:78:89:40:49:
37:42:0D:8F:F5:E8
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:old.peopletalk.ru
DNS:peopletalk.ru
DNS:s1-padm.peopletalk.ru
DNS:s1.peopletalk.ru
DNS:s2-padm.peopletalk.ru
DNS:s3-padm.peopletalk.ru
DNS:st.peopletalk.ru
DNS:www.peopletalk.ru
DNS:zabbix.peopletalk.ru
DNS:dev.peopletalk.ru
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 15th August, 2020
Content-Type: text/html; charset=UTF-8
Link: <https://peopletalk.ru/>; rel=shortlink
htmlcache: 1m
Vary: User-Agent
Set-Cookie: *

Whois Lookup

Created: 31st May, 2007
Changed:
Expires: 31st May, 2021
Registrar: REGTIME-RU
Status:
Nameservers: amy.ns.cloudflare.com
dilbert.ns.cloudflare.com
Owner Organization: Ltd \"Peopletalk\"
Full 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: PEOPLETALK.RU
nserver: amy.ns.cloudflare.com.
nserver: dilbert.ns.cloudflare.com.
state: REGISTERED, DELEGATED, VERIFIED
org: Ltd "Peopletalk"
registrar: REGTIME-RU
admin-contact: https://whois.webnames.ru
created: 2007-05-31T20:00:00Z
paid-till: 2021-05-31T21:00:00Z
free-date: 2021-07-02
source: TCI

Last updated on 2020-08-15T01:31:32Z

Nameservers

Name IP Address
amy.ns.cloudflare.com 108.162.192.101
dilbert.ns.cloudflare.com 173.245.59.155
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address