spaces.ru

spaces.ru is SSL secured

Free website and domain report on spaces.ru

Last Updated: 21st September, 2023 Update Now
Overview

Snoop Summary for spaces.ru

This is a free and comprehensive report about spaces.ru. Spaces.ru is hosted in Germany on a server with an IP address of 94.130.183.117, where the local currency is EUR and German is the local language. Our records indicate that spaces.ru is owned/operated by 'MT Group' Limited Liability Company. Spaces.ru has the potential to be earning an estimated $13 USD per day from advertising revenue. If spaces.ru was to be sold it would possibly be worth $9,742 USD (based on the daily revenue potential of the website over a 24 month period). Spaces.ru is quite popular with an estimated 4,678 daily unique visitors. This report was last updated 21st September, 2023.

About spaces.ru

Site Preview: spaces.ru spaces.ru
Title: Spaces
Description: Официальный сайт Спакес.ру (Spaces.ru). Это мобильная социальная сеть также известная как: спейсис, спейс, спайсес и spaces.im. На нашем сайте вы можете найти: зону обмена, музыку, сообщества, блоги, знакомства, чаты и форумы, объявления, онлайн-игры и популярные фото.
Keywords and Tags: mobile phone
Related Terms: confined spaces, how many spaces is a tab, living spaces, perfectoid spaces, servcorp coworking spaces, spaces, spaces and exchanges immigration usa, spaces.im, spaces.ru, sydney event spaces
Fav Icon:
Age: Over 17 years old
Domain Created: 6th June, 2006
Domain Updated:
Domain Expires: 6th June, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$9,742 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 129,030
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: 4,678
Monthly Visitors: 142,374
Yearly Visitors: 1,707,351
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $13 USD
Monthly Revenue: $406 USD
Yearly Revenue: $4,866 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: spaces.ru 9
Domain Name: spaces 6
Extension (TLD): ru 2
Expiry Check:

Page Speed Analysis

Average Load Time: 2.11 seconds
Load Time Comparison: Faster than 41% of sites

PageSpeed Insights

Avg. (All Categories) 82
Performance 92
Accessibility 90
Best Practices 85
SEO 100
PWA 44
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://spaces.im/
Updated: 26th December, 2021

3.17 seconds
First Contentful Paint (FCP)
49%
25%
26%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
92

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 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).
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://spaces.ru/
http/1.1
0
392.9430001881
542
0
301
text/html
https://spaces.im/
http/1.1
393.31200020388
2067.5420002081
15612
73093
200
text/html
Document
https://spac.me/css/custom/pc/b/main.css?16ccab22
http/1.1
2080.8350001462
3459.6400000155
37288
164201
200
text/css
Stylesheet
https://spac.me/css/custom/pc/b/guest/preload-pc.css?0ea6b8ad
http/1.1
2081.0200001579
3314.7230001632
19107
86637
200
text/css
Stylesheet
https://spac.me/js/touch/b/guest/entry-pc.js?1d908c29
http/1.1
3316.4320001379
4383.5540001746
112562
299884
200
application/x-javascript
Script
https://spac.me/i/head/gray/slipknot.png
http/1.1
3461.5410000551
4545.080000069
778
466
200
image/png
Image
https://spac.me/i/medal_silver.gif
http/1.1
3470.2469999902
4544.550999999
415
104
200
image/gif
Image
https://spac.me/i/em/1F1FA-1F1E6.png
http/1.1
3472.7520002052
3981.1180001125
767
480
200
image/webp
Image
https://spac.me/i/em/1F4DD.png
http/1.1
3472.9600001592
4378.9360001683
639
352
200
image/webp
Image
https://spac.me/i/em/1F539.png
http/1.1
3473.2790000271
4551.4650000259
683
396
200
image/webp
Image
https://mobtop.com/c/163.js
http/1.1
3473.5250000376
4306.165000191
901
680
200
application/x-javascript
Script
https://spac.me/i/bg/newyear.png
http/1.1
3482.1580001153
4538.1920000073
13081
12766
200
image/png
Image
https://spac.me/i/ico_logo_newyear.png?d3e894a4
http/1.1
3482.9950002022
4549.791000085
8791
8502
200
image/webp
Image
https://spac.me/i/ico_sidebar_pc.png?b8643366
http/1.1
3492.2120000701
4537.3980000149
6709
6420
200
image/webp
Image
https://spac.me/i/search_icon.png?r=1
http/1.1
3493.5500000138
4550.7050000597
514
228
200
image/webp
Image
data
3502.5560001377
3502.6450001169
0
68
200
image/png
Image
data
3507.9550000373
3508.0510000698
0
72
200
image/png
Image
https://spac.me/i/ico.png?6d761341
http/1.1
3511.0780000687
4649.6980001684
42640
42350
200
image/webp
Image
https://spac.me/i/tile_main.png?1ec39a8a
http/1.1
3512.9500001203
4139.1770001501
5055
4766
200
image/webp
Image
https://spac.me/i/e8f1a0ab524437bbd68ac6b6cec1f9a2/lmir_tenei.gif
http/1.1
3545.9559999872
4541.343000019
4743
4429
200
image/gif
Image
https://spac.me/i/5d4c11069936dbc4cf6d82b1520ddc8c/lneboskreby.gif
http/1.1
3549.1650002077
4380.5550001562
2484
2171
200
image/gif
Image
https://spac.me/i/bbc7bce0089dae302e0f360a40dce8d2/lmyferm.gif
http/1.1
3549.8950001784
4378.1890000682
4589
4275
200
image/gif
Image
https://spac.me/i/ico_thirdparty.png?bf8c70c2
http/1.1
3550.1000001095
4553.1690001953
3094
2806
200
image/webp
Image
https://mobtop.com/163.gif?rnd=1640478377582&ref=
http/1.1
4309.4880001154
5148.9750000183
1305
932
200
image/gif
Image
https://counter.yadro.ru/hit?t41.6;r;s800*600*24;uhttps%3A//spaces.im/;0.5712841410474008
http/1.1
4662.0760001242
5330.8360001538
602
0
302
text/html
https://ts.spac.me/tpic/3169347294/1640477700/75522b89cf601a88b8cd1ff37b30e66d/310748920.p.81.80.0.jpg
http/1.1
4813.0560000427
5642.4530001823
2807
2515
200
image/jpeg
Image
https://ts.spac.me/tpic/1201991480/1640477700/03494e41d0c2ece8fea22ef42e62c0ee/310763903.p.81.80.0.jpg
http/1.1
4813.3450001478
5669.2320001312
3361
3069
200
image/jpeg
Image
https://ts.spac.me/tfil/2279493387/1640477700/73bb2f7f9ab4013c1cb80925ff6aa866/89213473.f.81.80.0.jpg
http/1.1
4813.771000132
5643.0220000912
3146
2854
200
image/jpeg
Image
https://ts.spac.me/tpic/1043253408/1640477700/64c6e66425ab059e606351d510aabad2/310745262.p.81.80.0.jpg
http/1.1
4814.0269999858
5645.104000112
1956
1664
200
image/jpeg
Image
https://ts.spac.me/tpic/3868365779/1640477700/974527e044710fc8964ce5d56fb3816d/310722452.p.81.80.0.jpg
http/1.1
4814.2480000388
7339.5370000508
2940
2648
200
image/jpeg
Image
https://ts.spac.me/tpic/3829345634/1640477700/a50b5c9ff77e7ce4ed5dda9bde589354/310743556.p.81.80.0.jpg
http/1.1
4814.5010001026
5648.0040000752
3465
3173
200
image/jpeg
Image
https://ts.spac.me/tfil/83338435/1640477700/64246b5f51fa139a9cb821300dde4fea/89213681.f.81.80.0.jpg
http/1.1
4814.7800001316
5643.7700001989
3640
3348
200
image/jpeg
Image
https://ts.spac.me/tpic/2109620463/1640477700/e98a9027421aed73dbece26fd8108068/310719430.p.129.128.0.jpg
http/1.1
4815.07900008
5644.7530000005
6064
5772
200
image/jpeg
Image
https://ts.spac.me/tpic/3231461772/1640477700/8ac078ec29bd38e63c0e5403ff999918/310740773.p.129.128.0.jpg
http/1.1
4815.4980000108
5641.7880000081
6474
6182
200
image/jpeg
Image
https://counter.yadro.ru/hit?q;t41.6;r;s800*600*24;uhttps%3A//spaces.im/;0.5712841410474008
http/1.1
5331.8730001338
5994.0400000196
590
104
200
image/gif
Image
https://spaces.im/api/uobj/view/?_=2
9816.0390001722
0
0
-1
XHR
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)
2118.565
8.458
3509.093
7.673
3522.142
15.663
3539.292
8.785
3556.549
14.556
3577.015
17.558
4449.543
9.202
4676.784
6.765
4853.687
5.79
4876.431
14.624
4891.071
6.677
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Spaces.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Spaces.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Spaces.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Spaces.ru should consider minifying JS files.
Reduce unused CSS — Potential savings of 50 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Spaces.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://spac.me/css/custom/pc/b/main.css?16ccab22
37288
32693
https://spac.me/css/custom/pc/b/guest/preload-pc.css?0ea6b8ad
19107
18149
Reduce unused JavaScript — Potential savings of 68 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://spac.me/js/touch/b/guest/entry-pc.js?1d908c29
112562
69476
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 10 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://spac.me/i/bg/newyear.png
12766
9914.95
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.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Spaces.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://spaces.ru/
190
https://spaces.im/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Spaces.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 10 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://spac.me/js/touch/b/guest/entry-pc.js?1d908c29
9973
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 310 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://spac.me/js/touch/b/guest/entry-pc.js?1d908c29
112562
https://spac.me/i/ico.png?6d761341
42640
https://spac.me/css/custom/pc/b/main.css?16ccab22
37288
https://spac.me/css/custom/pc/b/guest/preload-pc.css?0ea6b8ad
19107
https://spaces.im/
15612
https://spac.me/i/bg/newyear.png
13081
https://spac.me/i/ico_logo_newyear.png?d3e894a4
8791
https://spac.me/i/ico_sidebar_pc.png?b8643366
6709
https://ts.spac.me/tpic/3231461772/1640477700/8ac078ec29bd38e63c0e5403ff999918/310740773.p.129.128.0.jpg
6474
https://ts.spac.me/tpic/2109620463/1640477700/e98a9027421aed73dbece26fd8108068/310719430.p.129.128.0.jpg
6064
Uses efficient cache policy on static assets — 1 resource found
Spaces.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://mobtop.com/c/163.js
0
901
Avoids an excessive DOM size — 814 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
814
Maximum DOM Depth
22
Maximum Child Elements
15
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Spaces.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.1 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://spaces.im/
156.978
5.668
5.22
https://spac.me/js/touch/b/guest/entry-pc.js?1d908c29
126.44
104.112
4.587
Minimizes main-thread work — 0.3 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
114.213
Other
74.679
Style & Layout
61.001
Rendering
56.206
Parse HTML & CSS
23.71
Script Parsing & Compilation
10.117
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 — 34 requests • 310 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
34
317344
Image
26
130730
Script
2
113463
Stylesheet
2
56395
Document
1
15612
Other
3
1144
Media
0
0
Font
0
0
Third-party
32
301732
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)
1192
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 spaces.ru on mobile screens.

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.

Other

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Spaces.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://spac.me/css/custom/pc/b/main.css?16ccab22
37288
270
https://spac.me/css/custom/pc/b/guest/preload-pc.css?0ea6b8ad
19107
270

Metrics

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

Other

Reduce initial server response time — Root document took 1,680 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://spaces.im/
1675.222
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://mobtop.com/163.gif?rnd=1640478377582&ref=
90

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of spaces.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.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.

Names and labels

Buttons 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.
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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<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.

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.
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.

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"]`
Spaces.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

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.

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.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that spaces.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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

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 `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://spac.me/js/touch/b/guest/entry-pc.js?1d908c29
https://spac.me/js/touch/b/guest/entry-pc.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://spaces.ru/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
80 x 80
1 x 1
80 x 80
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for spaces.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 spaces.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.
44

PWA

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

Installable

Web app manifest and service worker 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.

PWA Optimized

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 spaces.ru on mobile screens.

PWA Optimized

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.
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
Does not provide 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.
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) 83
Performance 86
Accessibility 95
Best Practices 85
SEO 100
PWA 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://spaces.im/
Updated: 26th December, 2021

3.21 seconds
First Contentful Paint (FCP)
47%
26%
27%

0.02 seconds
First Input Delay (FID)
96%
3%
1%

Simulate loading on mobile
86

Performance

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

Metrics

Time to Interactive — 2.5 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://spaces.ru/
http/1.1
0
1781.8330004811
544
0
301
text/html
https://spaces.im/
http/1.1
1782.1730002761
3493.9630003646
14594
61202
200
text/html
Document
https://spac.me/css/custom/touch/b/main.css?16ccab22
http/1.1
3511.706000194
4870.6579999998
35745
155373
200
text/css
Stylesheet
https://spac.me/css/custom/touch/b/guest/preload-touch.css?c824f4f7
http/1.1
3512.2110005468
4721.9710005447
19109
86640
200
text/css
Stylesheet
https://spac.me/js/touch/b/guest/entry.js?b7c1c457
http/1.1
4723.3720002696
6315.639000386
102457
269980
200
application/x-javascript
Script
https://spac.me/i/head/gray/slipknot.png
http/1.1
4872.2719997168
5933.8450003415
778
466
200
image/png
Image
https://spac.me/i/medal_silver.gif
http/1.1
4878.6059999838
5535.2499997243
415
104
200
image/gif
Image
https://spac.me/i/em/1F1FA-1F1E6.png
http/1.1
4878.7920000032
5960.5999998748
767
480
200
image/webp
Image
https://ts.spac.me/tpic/1870131203/1640477700/a0060f96ee04dfcb7492e80909b34935/310629870.p.81.80.0.jpg
http/1.1
4878.9840005338
5388.8570005074
3849
3557
200
image/jpeg
Image
https://ts.spac.me/tpic/4223462150/1640477700/4b11daed2a6031d24dc6f024328b132c/261040489.p.81.80.0.jpg
http/1.1
4879.2150001973
5388.5810002685
3456
3164
200
image/jpeg
Image
https://ts.spac.me/tpic/2191469673/1640477700/8d03dd77028a6b0c41755ccbebd58b01/310651506.p.81.80.0.jpg
http/1.1
4879.4609997422
5392.94099994
3242
2950
200
image/jpeg
Image
https://mobtop.com/c/163.js
http/1.1
4879.6570003033
5696.1030000821
901
680
200
application/x-javascript
Script
data
4888.966999948
4889.0460003167
0
68
200
image/png
Image
https://spac.me/i/ico_2x.png?c8700e66
http/1.1
4893.1900002062
6353.4510005265
88449
88158
200
image/webp
Image
https://spac.me/i/ico_header_logo_newyear_2x.png?2a4f9fe4
http/1.1
4893.3870000765
5942.1580005437
10396
10106
200
image/webp
Image
https://spac.me/i/search_icon.png?r=1
http/1.1
4894.4520000368
5932.9500002787
514
228
200
image/webp
Image
https://spac.me/i/tile_main_2x.png?03b5bf62
http/1.1
4894.9640002102
5938.4319996461
10314
10024
200
image/webp
Image
data
4916.5260000154
4916.6099997237
0
72
200
image/png
Image
https://spac.me/i/ico_thirdparty_2x.png?2b6e1e52
http/1.1
4926.5489997342
5974.663999863
6157
5868
200
image/webp
Image
https://spac.me/i/e8f1a0ab524437bbd68ac6b6cec1f9a2/lmir_tenei.gif
http/1.1
4943.2749999687
5386.1149996519
4743
4429
200
image/gif
Image
https://spac.me/i/5d4c11069936dbc4cf6d82b1520ddc8c/lneboskreby.gif
http/1.1
4943.7319999561
5557.1729997173
2484
2171
200
image/gif
Image
https://spac.me/i/bbc7bce0089dae302e0f360a40dce8d2/lmyferm.gif
http/1.1
4944.4070002064
5958.2829996943
4589
4275
200
image/gif
Image
https://mobtop.com/163.gif?rnd=1640478414215&ref=
http/1.1
5700.7680004463
6223.224000074
1305
932
200
image/gif
Image
https://counter.yadro.ru/hit?t41.6;r;s360*640*24;uhttps%3A//spaces.im/;0.8623379946424501
http/1.1
6548.8489996642
7213.3210003376
602
0
302
text/html
https://counter.yadro.ru/hit?q;t41.6;r;s360*640*24;uhttps%3A//spaces.im/;0.8623379946424501
http/1.1
7213.557000272
7874.5020003989
590
104
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)
3539.144
11.614
3551.575
5.902
4913.179
5.573
4921.248
5.957
4933.304
14.983
4951.005
5.537
4964.748
20.481
6370.25
8.423
6551.675
9.976
6714.986
5.298
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Spaces.ru should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Spaces.ru should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Spaces.ru should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Spaces.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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Spaces.ru should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://spaces.ru/
630
https://spaces.im/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Spaces.ru should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 309 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://spac.me/js/touch/b/guest/entry.js?b7c1c457
102457
https://spac.me/i/ico_2x.png?c8700e66
88449
https://spac.me/css/custom/touch/b/main.css?16ccab22
35745
https://spac.me/css/custom/touch/b/guest/preload-touch.css?c824f4f7
19109
https://spaces.im/
14594
https://spac.me/i/ico_header_logo_newyear_2x.png?2a4f9fe4
10396
https://spac.me/i/tile_main_2x.png?03b5bf62
10314
https://spac.me/i/ico_thirdparty_2x.png?2b6e1e52
6157
https://spac.me/i/e8f1a0ab524437bbd68ac6b6cec1f9a2/lmir_tenei.gif
4743
https://spac.me/i/bbc7bce0089dae302e0f360a40dce8d2/lmyferm.gif
4589
Uses efficient cache policy on static assets — 1 resource found
Spaces.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://mobtop.com/c/163.js
0
901
Avoids an excessive DOM size — 686 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
686
Maximum DOM Depth
22
Maximum Child Elements
15
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Spaces.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.4 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://spaces.im/
437.284
22.94
18.664
https://spac.me/js/touch/b/guest/entry.js?b7c1c457
343.624
300.268
16.408
Unattributable
137.428
11.584
0.524
Minimizes main-thread work — 1.0 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
340.928
Other
229.272
Style & Layout
149.144
Rendering
134.468
Parse HTML & CSS
71.548
Script Parsing & Compilation
36.164
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 — 23 requests • 309 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
23
316000
Image
16
142048
Script
2
103358
Stylesheet
2
54854
Document
1
14594
Other
2
1146
Media
0
0
Font
0
0
Third-party
22
301406
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)
1192
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
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
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 spaces.ru on mobile screens.

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 — 2.5 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 2.6 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 2.5 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 50 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Spaces.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://spac.me/css/custom/touch/b/main.css?16ccab22
35745
32413
https://spac.me/css/custom/touch/b/guest/preload-touch.css?c824f4f7
19109
18337
Reduce unused JavaScript — Potential savings of 68 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://spac.me/js/touch/b/guest/entry.js?b7c1c457
102457
69374
Avoid serving legacy JavaScript to modern browsers — Potential savings of 10 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://spac.me/js/touch/b/guest/entry.js?b7c1c457
10099

Metrics

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

Other

Eliminate render-blocking resources — Potential savings of 1,070 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Spaces.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://spac.me/css/custom/touch/b/main.css?16ccab22
35745
1080
https://spac.me/css/custom/touch/b/guest/preload-touch.css?c824f4f7
19109
930
Reduce initial server response time — Root document took 1,710 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://spaces.im/
1712.781
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://mobtop.com/163.gif?rnd=1640478414215&ref=
First Contentful Paint (3G) — 5490 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of spaces.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.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.

Names and labels

Buttons 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.
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.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links 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.
`<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.

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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
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.

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"]`
Spaces.ru may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Navigation

Heading elements are not 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.
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.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that spaces.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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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 `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://spac.me/js/touch/b/guest/entry.js?b7c1c457
https://spac.me/js/touch/b/guest/entry.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://spaces.ru/
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for spaces.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 spaces.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
Tap targets are sized appropriately — 100% 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.

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.
50

PWA

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

Installable

Web app manifest and service worker 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.

PWA Optimized

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 spaces.ru on mobile screens.

PWA Optimized

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.
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
Does not provide 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.
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: 94.130.183.117
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Name IP Address
Hetzner Online GmbH
Registration

Domain Registrant

Private Registration: No
Name:
Organization: 'MT Group' Limited Liability Company
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:
WOT Trustworthiness: 90/100
WOT Child Safety: 80/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: spaces.im
Issued By: R3
Valid From: 11th December, 2021
Valid To: 11th March, 2022
Subject: CN = spaces.im
Hash: c9ceeb1b
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03DAE5FDB3F9BB11CCD39B26A55CBA8BEC37
Serial Number (Hex): 03DAE5FDB3F9BB11CCD39B26A55CBA8BEC37
Valid From: 11th December, 2024
Valid To: 11th March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
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://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Dec 11 10:50:28.574 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:F1:F0:28:FC:0E:EB:24:26:94:7C:5F:
93:AF:73:AF:66:85:4F:14:61:7D:64:13:74:BF:4F:84:
12:CC:81:8A:78:02:21:00:E2:1E:88:A1:B6:2F:B5:21:
8B:0F:78:0D:46:F7:BF:0B:D0:28:97:30:F4:90:14:79:
5A:DE:FA:F1:84:75:F0:55
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Dec 11 10:50:28.975 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:58:D4:87:EE:CB:3E:41:0C:5E:7C:90:8A:
68:92:85:12:B6:28:E7:88:C9:CD:39:5C:63:13:17:45:
39:63:72:C0:02:20:4B:68:80:2A:EB:0A:73:1F:46:80:
73:F2:FC:DF:11:3E:D1:2C:27:33:F6:23:37:14:A5:9C:
3E:EB:D0:90:51:79
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:spaces.im
Technical

DNS Lookup

A Records

Host IP Address Class TTL
spaces.ru. 94.130.183.117 IN 1800

NS Records

Host Nameserver Class TTL
spaces.ru. ns.spaces.ru. IN 1800
spaces.ru. ns4-l2.nic.ru. IN 1800

MX Records

Priority Host Server Class TTL
10 spaces.ru. mail.spaces.ru. IN 1800

SOA Records

Domain Name Primary NS Responsible Email TTL
spaces.ru. ns.spaces.ru. nickolay.spaces.ru. 1800

TXT Records

Host Value Class TTL
spaces.ru. yandex-verification: IN 1800
spaces.ru. v=spf1 IN 1800
spaces.ru. google-site-verification=_ZW-LWlgcTgWW1GWef4qRGRht9LQqfrALrp9RmIbZ3w IN 1800

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.12.2
Date: 26th December, 2021
Content-Type: text/html; charset=utf-8
Expires: 19th November, 1981
Cache-Control: max-age=3600, no-cache, no-store, must-revalidate
Content-Length: 73133
Connection: keep-alive
X-Frame-Options: deny
Vary: User-Agent,Accept-Encoding
Pragma: no-cache
Set-Cookie: *

Whois Lookup

Created: 6th June, 2006
Changed:
Expires: 6th June, 2022
Registrar: RU-CENTER-RU
Status:
Nameservers: ns.spaces.ru
ns2.spaces.ru
ns4-l2.nic.ru
Owner Organization: 'MT Group' Limited Liability Company
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: SPACES.RU
nserver: ns2.spaces.ru. 176.9.36.212
nserver: ns4-l2.nic.ru.
nserver: ns.spaces.ru. 91.142.87.195
state: REGISTERED, DELEGATED, VERIFIED
org: 'MT Group' Limited Liability Company
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 2006-06-06T20:00:00Z
paid-till: 2022-06-06T21:00:00Z
free-date: 2022-07-08
source: TCI

Last updated on 2021-12-26T00:21:31Z

Nameservers

Name IP Address
ns.spaces.ru 91.142.87.195
ns2.spaces.ru 176.9.36.212
ns4-l2.nic.ru 91.217.20.20
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5

Sites hosted on the same IP address