40.7 sec in total
1.2 sec
18.3 sec
21.2 sec
Click here to check amazing Richtime content for Russia. Otherwise, check out these important facts you probably never knew about richtime.ru
Здесь можно купить оригинальные наручные и интерьерные часы известных брендов. Выгодные цены, доставка по России.
Visit richtime.ruWe analyzed Richtime.ru page load time and found that the first response time was 1.2 sec and then it took 39.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
richtime.ru performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value14.9 s
0/100
25%
Value8.0 s
22/100
10%
Value630 ms
47/100
30%
Value0.063
97/100
15%
Value12.6 s
14/100
10%
1179 ms
629 ms
533 ms
534 ms
426 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 74% of them (28 requests) were addressed to the original Richtime.ru, 11% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Richtime.ru.
Page size can be reduced by 596.3 kB (67%)
888.2 kB
291.8 kB
In fact, the total size of Richtime.ru main page is 888.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. HTML takes 602.9 kB which makes up the majority of the site volume.
Potential reduce by 543.3 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 140.2 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 543.3 kB or 90% of the original size.
Potential reduce by 2.1 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Richtime needs image optimization as it can save up to 2.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 15.7 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 35.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Richtime.ru needs all CSS files to be minified and compressed as it can save up to 35.2 kB or 31% of the original size.
Number of requests can be reduced by 19 (66%)
29
10
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Richtime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
richtime.ru
1179 ms
richtime.ru
629 ms
ui.font.opensans.min.css
533 ms
main.popup.bundle.min.css
534 ms
css
426 ms
template_c7e92a984a6367497e6cc1584e9db499_v1.css
957 ms
core.min.js
957 ms
kernel_main_v1.js
758 ms
dexie3.bundle.min.js
747 ms
core_ls.min.js
743 ms
core_frame_cache.min.js
745 ms
protobuf.min.js
3296 ms
model.min.js
3296 ms
rest.client.min.js
3296 ms
pull.client.min.js
3295 ms
main.popup.bundle.min.js
3754 ms
tag.js
4050 ms
currency-core.bundle.min.js
3966 ms
core_currency.min.js
3753 ms
cphttprequest.min.js
3752 ms
template_d39f53ebb7945a816194df18fdb46485_v1.js
5071 ms
script.js
3464 ms
ba.js
714 ms
logotype.png
1228 ms
Richtime_logo_colored_black.svg
603 ms
picture.loading.svg
727 ms
gj640fq5a994c9orso3yh0kmodn1urbv.png
521 ms
sync_cookie_image_decide
292 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLs.woff
1351 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXx-p7K4GLs.woff
1194 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aXx-p7K4GLs.woff
1194 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLs.woff
1192 ms
a4051eb32350f3de0547a4c2dc1e9b79.svg
709 ms
1
316 ms
logotype.png
427 ms
icons_color_round.svg
486 ms
icons_2.png
443 ms
client.js
562 ms
richtime.ru accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
richtime.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
richtime.ru SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richtime.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Richtime.ru main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
richtime.ru
Open Graph description is not detected on the main page of Richtime. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: