Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 57

    SEO

    Google-friendlier than
    20% of websites

history.by

IH NASB | The State Scientific Institution «The Institute of History of the National Academy of Sciences of Belarus»

Page Load Speed

13.5 sec in total

First Response

1.8 sec

Resources Loaded

10.4 sec

Page Rendered

1.3 sec

history.by screenshot

About Website

Click here to check amazing History content for Belarus. Otherwise, check out these important facts you probably never knew about history.by

| The State Scientific Institution «The Institute of History of the National Academy of Sciences of Belarus»

Visit history.by

Key Findings

We analyzed History.by page load time and found that the first response time was 1.8 sec and then it took 11.7 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

history.by performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value3,010 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.144

78/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

en

1795 ms

normalize.css

232 ms

style.css

233 ms

prettyPhoto.css

255 ms

grid.css

259 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 88% of them (51 requests) were addressed to the original History.by, 7% (4 requests) were made to Nasb.gov.by and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain History.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.1 kB (7%)

Content Size

859.8 kB

After Optimization

798.7 kB

In fact, the total size of History.by main page is 859.8 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. 45% of websites need less resources to load. Images take 757.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 39.8 kB

  • Original 49.4 kB
  • After minification 46.9 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 39.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 15.9 kB

  • Original 757.1 kB
  • After minification 741.2 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. History images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 30.8 kB
  • After minification 30.8 kB
  • After compression 30.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

-24%

Potential reduce by 5.4 kB

  • Original 22.5 kB
  • After minification 22.5 kB
  • After compression 17.1 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. History.by needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (54%)

Requests Now

52

After Optimization

24

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

Accessibility Review

history.by accessibility score

80

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

history.by best practices score

67

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

Browser errors were logged to the console

SEO Factors

history.by SEO score

57

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise History.by can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that History.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 History. 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: