Tools & Wizards About Us

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

63.ru

Новости Самары - главные новости сегодня | 63.ру - новости Самары

Page Load Speed

15.8 sec in total

First Response

1.2 sec

Resources Loaded

13.7 sec

Page Rendered

879 ms

About Website

Welcome to 63.ru homepage info - get ready to check 63 best content for Russia right away, or after learning these important things about 63.ru

Последние свежие новости Самары и Самарской области за сегодня - онлайн на сайте 63.ру

Visit 63.ru

Key Findings

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

Performance Metrics

63.ru performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value4,940 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value27.7 s

0/100

10%

Network Requests Diagram

63.ru

1246 ms

jquery-1.9.1.min.js

960 ms

jquery-1.8.3.min.js

1048 ms

jquery.js

975 ms

jquery.xdomainrequest.min.js

370 ms

Our browser made a total of 252 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original 63.ru, 29% (73 requests) were made to I.sdska.ru and 25% (64 requests) were made to Reklama.ngs.ru. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Z19.d.sdska.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (47%)

Content Size

3.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of 63.ru main page is 3.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 314.0 kB

  • Original 378.7 kB
  • After minification 375.0 kB
  • After compression 64.7 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 314.0 kB or 83% of the original size.

Image Optimization

-19%

Potential reduce by 263.1 kB

  • Original 1.4 MB
  • After minification 1.1 MB

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, 63 needs image optimization as it can save up to 263.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 855.1 kB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 422.1 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 855.1 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 136 (56%)

Requests Now

242

After Optimization

106

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

63.ru accessibility score

57

Accessibility Issues

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

63.ru best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

63.ru SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

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