Tools & Wizards About Us
samaraphone.ru screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

samaraphone.ru

Телефонная база Самары позволит узнать телефон по адресу; номера телефонов компаний, организаций, предприятий и фирм Самары

Page Load Speed

3.5 sec in total

First Response

506 ms

Resources Loaded

2.8 sec

Page Rendered

177 ms

samaraphone.ru screenshot

About Website

Click here to check amazing Samaraphone content for Russia. Otherwise, check out these important facts you probably never knew about samaraphone.ru

В телефонной базе Самары и Приволжского федерального округа вы всегда можете узнать адрес по телефону организации

Visit samaraphone.ru

Key Findings

We analyzed Samaraphone.ru page load time and found that the first response time was 506 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

samaraphone.ru performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

samaraphone.ru

506 ms

samara.spravinfo.ru

715 ms

spravinfo.css

267 ms

Form.css

281 ms

adsbygoogle.js

163 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Samaraphone.ru, 78% (21 requests) were made to Samara.spravinfo.ru and 7% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.5 kB (8%)

Content Size

411.5 kB

After Optimization

378.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 32.8 kB

  • Original 42.4 kB
  • After minification 42.2 kB
  • After compression 9.5 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 32.8 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.9 kB
  • After minification 5.9 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. Samaraphone images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 112 B

  • Original 359.9 kB
  • After minification 359.9 kB
  • After compression 359.8 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.

CSS Optimization

-18%

Potential reduce by 580 B

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 2.7 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. Samaraphone.ru needs all CSS files to be minified and compressed as it can save up to 580 B or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (44%)

Requests Now

25

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

samaraphone.ru

samaraphone.ru

506 ms

samara.spravinfo.ru

samara.spravinfo.ru

715 ms

spravinfo.css

spravinfo.css

267 ms

Form.css

Form.css

281 ms

adsbygoogle.js

adsbygoogle.js

163 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

702 ms

Form.js

Form.js

283 ms

context.js

context.js

1048 ms

show_ads_impl.js

show_ads_impl.js

300 ms

logo2020.png

logo2020.png

254 ms

looking.gif

looking.gif

257 ms

bashkiriya.gif

bashkiriya.gif

284 ms

kirovskaya-oblast.gif

kirovskaya-oblast.gif

284 ms

mariy-el.gif

mariy-el.gif

282 ms

mordoviya.gif

mordoviya.gif

285 ms

nizhegorodskaya-oblast.gif

nizhegorodskaya-oblast.gif

512 ms

orenburgskaya-oblast.gif

orenburgskaya-oblast.gif

548 ms

penzenskaya-oblast.gif

penzenskaya-oblast.gif

538 ms

permskiy-kray.gif

permskiy-kray.gif

541 ms

samarskaya-oblast.gif

samarskaya-oblast.gif

553 ms

saratovskaya-oblast.gif

saratovskaya-oblast.gif

556 ms

tatarstan.gif

tatarstan.gif

775 ms

udmurtiya.gif

udmurtiya.gif

793 ms

ulyanovskaya-oblast.gif

ulyanovskaya-oblast.gif

806 ms

chuvashiya.gif

chuvashiya.gif

819 ms

zrt_lookup.html

zrt_lookup.html

25 ms

tag.js

tag.js

899 ms

Accessibility Review

samaraphone.ru accessibility score

96

Accessibility Issues

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

samaraphone.ru SEO score

94

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Samaraphone.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 Samaraphone.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

samaraphone.ru

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