Tools & Wizards About Us
moscowpage.ru screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    78% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

moscowpage.ru

Телефонный справочник - Москва и Московская область

Page Load Speed

3.4 sec in total

First Response

920 ms

Resources Loaded

2.4 sec

Page Rendered

149 ms

moscowpage.ru screenshot

About Website

Visit moscowpage.ru now to see the best up-to-date Moscowpage content for Russia and also check out these interesting facts you probably never knew about moscowpage.ru

Москва и Московская область - Телефонный справочник компаний, удобный отраслевой рубрикатор. Отзывы о компаниях, контакты, карта проезда.

Visit moscowpage.ru

Key Findings

We analyzed Moscowpage.ru page load time and found that the first response time was 920 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

moscowpage.ru performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

moscowpage.ru

920 ms

application-4e83e4834b68ab0d2c13f4a6857b51d3.css

46 ms

application-a315aa93790a34a5fe0302a0f98c4f3b.js

309 ms

jquery-ui.min.js

30 ms

adsbygoogle.js

72 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 11% of them (4 requests) were addressed to the original Moscowpage.ru, 17% (6 requests) were made to Tpc.googlesyndication.com and 14% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (920 ms) belongs to the original domain Moscowpage.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 50.1 kB (21%)

Content Size

237.4 kB

After Optimization

187.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Moscowpage.ru main page is 237.4 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. 35% of websites need less resources to load. Javascripts take 196.3 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 21.2 kB

  • Original 30.1 kB
  • After minification 27.1 kB
  • After compression 8.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.2 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 15 B

  • Original 1.6 kB
  • After minification 1.5 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. Moscowpage images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 28.8 kB

  • Original 196.3 kB
  • After minification 196.1 kB
  • After compression 167.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 28.8 kB or 15% of the original size.

CSS Optimization

-2%

Potential reduce by 184 B

  • Original 9.5 kB
  • After minification 9.5 kB
  • After compression 9.3 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. Moscowpage.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (47%)

Requests Now

30

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moscowpage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

moscowpage.ru

moscowpage.ru

920 ms

application-4e83e4834b68ab0d2c13f4a6857b51d3.css

application-4e83e4834b68ab0d2c13f4a6857b51d3.css

46 ms

application-a315aa93790a34a5fe0302a0f98c4f3b.js

application-a315aa93790a34a5fe0302a0f98c4f3b.js

309 ms

jquery-ui.min.js

jquery-ui.min.js

30 ms

adsbygoogle.js

adsbygoogle.js

72 ms

google_custom_search_smnar.gif

google_custom_search_smnar.gif

37 ms

logo-b0e4c1e9ac4527ec394e38693a519d9d.png

logo-b0e4c1e9ac4527ec394e38693a519d9d.png

175 ms

branding.css

branding.css

12 ms

branding.css

branding.css

22 ms

google_custom_search_smnar.gif

google_custom_search_smnar.gif

116 ms

zrt_lookup.html

zrt_lookup.html

37 ms

show_ads_impl.js

show_ads_impl.js

79 ms

ga.js

ga.js

18 ms

__utm.gif

__utm.gif

16 ms

hit

hit

237 ms

cookie.js

cookie.js

45 ms

integrator.js

integrator.js

54 ms

ads

ads

481 ms

load_preloaded_resource.js

load_preloaded_resource.js

40 ms

abg_lite.js

abg_lite.js

32 ms

window_focus.js

window_focus.js

40 ms

rx_lidar.js

rx_lidar.js

52 ms

qs_click_protection.js

qs_click_protection.js

40 ms

99d351374812bfb865cd4e83ebb83e02.js

99d351374812bfb865cd4e83ebb83e02.js

44 ms

icon.png

icon.png

22 ms

s

s

5 ms

css

css

26 ms

activeview

activeview

68 ms

sodar

sodar

25 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

14 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

18 ms

sodar2.js

sodar2.js

21 ms

runner.html

runner.html

7 ms

aframe

aframe

24 ms

BcUHUABoavvpRAX3o-C5BfAq8AHsMXRVb9HgeqDHxZ8.js

BcUHUABoavvpRAX3o-C5BfAq8AHsMXRVb9HgeqDHxZ8.js

4 ms

Accessibility Review

moscowpage.ru accessibility score

78

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

moscowpage.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

moscowpage.ru SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moscowpage.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Moscowpage.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.

Social Sharing Optimization

moscowpage.ru

Open Graph description is not detected on the main page of Moscowpage. 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: