Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

pressball.by

Прессбол - новости белорусского спорта

Page Load Speed

7.4 sec in total

First Response

405 ms

Resources Loaded

6 sec

Page Rendered

988 ms

pressball.by screenshot

About Website

Welcome to pressball.by homepage info - get ready to check Pressball best content for Belarus right away, or after learning these important things about pressball.by

Прессбол - новости белорусского спорта

Visit pressball.by

Key Findings

We analyzed Pressball.by page load time and found that the first response time was 405 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pressball.by performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value6,220 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value34.7 s

0/100

10%

Network Requests Diagram

pressball.by

405 ms

www.pressball.by

768 ms

stl.css

401 ms

jquery-ui.css

282 ms

carousel_online.css

290 ms

Our browser made a total of 210 requests to load all elements on the main page. We found that 60% of them (126 requests) were addressed to the original Pressball.by, 6% (13 requests) were made to Vk.com and 4% (8 requests) were made to Content.adriver.ru. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Pressball.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (21%)

Content Size

8.8 MB

After Optimization

6.9 MB

In fact, the total size of Pressball.by main page is 8.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 150.9 kB

  • Original 179.7 kB
  • After minification 145.1 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 34.5 kB, which is 19% 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 150.9 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 337.7 kB

  • Original 6.9 MB
  • After minification 6.6 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. Pressball images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 849.1 kB

  • Original 1.1 MB
  • After minification 832.3 kB
  • After compression 245.6 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 849.1 kB or 78% of the original size.

CSS Optimization

-89%

Potential reduce by 503.7 kB

  • Original 569.0 kB
  • After minification 459.2 kB
  • After compression 65.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. Pressball.by needs all CSS files to be minified and compressed as it can save up to 503.7 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (41%)

Requests Now

198

After Optimization

117

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

Accessibility Review

pressball.by accessibility score

64

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

pressball.by best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pressball.by SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Pressball.by 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 Pressball.by 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 data is detected on the main page of Pressball. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: