Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

stom.by

Новости - Белорусский стоматологический портал

Page Load Speed

3.5 sec in total

First Response

856 ms

Resources Loaded

2.5 sec

Page Rendered

209 ms

stom.by screenshot

About Website

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

Один из крупнейших стоматологических сайтов STOM.BY включает специальную и тематическую информацию как для пациентов, так и для врачей и студентов.

Visit stom.by

Key Findings

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

Performance Metrics

stom.by performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

stom.by

856 ms

bootstrap.min.css

159 ms

template.css

318 ms

bootstrap-fileupload.css

316 ms

jquery.min.js

478 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 86% of them (30 requests) were addressed to the original Stom.by, 11% (4 requests) were made to Site.yandex.net and 3% (1 request) were made to Yastatic.net. The less responsive or slowest element that took the longest time to load (949 ms) belongs to the original domain Stom.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 384.8 kB (48%)

Content Size

797.1 kB

After Optimization

412.3 kB

In fact, the total size of Stom.by main page is 797.1 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. 30% of websites need less resources to load. Javascripts take 522.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 27.3 kB

  • Original 36.7 kB
  • After minification 36.1 kB
  • After compression 9.4 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 27.3 kB or 74% of the original size.

Image Optimization

-9%

Potential reduce by 18.9 kB

  • Original 217.0 kB
  • After minification 198.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. Stom images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 322.9 kB

  • Original 522.9 kB
  • After minification 515.0 kB
  • After compression 200.0 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 322.9 kB or 62% of the original size.

CSS Optimization

-76%

Potential reduce by 15.6 kB

  • Original 20.5 kB
  • After minification 19.0 kB
  • After compression 4.9 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. Stom.by needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (35%)

Requests Now

34

After Optimization

22

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

Accessibility Review

stom.by accessibility score

59

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

stom.by 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

SEO Factors

stom.by SEO score

54

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

High

robots.txt is not valid

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

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 Stom.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 Stom.by 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

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