Tools & Wizards About Us
psu.by screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

psu.by

Home - Полоцкий государственный университет имени Евфросинии Полоцкой

Page Load Speed

5.5 sec in total

First Response

465 ms

Resources Loaded

4.9 sec

Page Rendered

121 ms

psu.by screenshot

About Website

Visit psu.by now to see the best up-to-date Psu content for Belarus and also check out these interesting facts you probably never knew about psu.by

Сайт Полоцкого государственного университета имени Евфросинии Полоцкой. Условия поступления, довузовская подготовка. Описание факультетов и специальностей. Архив новостей и событий.

Visit psu.by

Key Findings

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

Performance Metrics

psu.by performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

psu.by

465 ms

psu.by

515 ms

www.psu.by

465 ms

446 ms

jquery-3.7.0.min.js

324 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that all of those requests were addressed to Psu.by and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Psu.by.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (79%)

Content Size

1.3 MB

After Optimization

261.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Psu.by main page is 1.3 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. 50% of websites need less resources to load. CSS take 710.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 43.0 kB

  • Original 52.9 kB
  • After minification 50.1 kB
  • After compression 9.9 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 43.0 kB or 81% of the original size.

Image Optimization

-28%

Potential reduce by 20.3 kB

  • Original 73.1 kB
  • After minification 52.8 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. Obviously, Psu needs image optimization as it can save up to 20.3 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-77%

Potential reduce by 336.7 kB

  • Original 436.4 kB
  • After minification 432.5 kB
  • After compression 99.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 336.7 kB or 77% of the original size.

CSS Optimization

-86%

Potential reduce by 610.9 kB

  • Original 710.4 kB
  • After minification 502.6 kB
  • After compression 99.4 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. Psu.by needs all CSS files to be minified and compressed as it can save up to 610.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (66%)

Requests Now

74

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

psu.by

psu.by

465 ms

psu.by

psu.by

515 ms

www.psu.by

www.psu.by

465 ms

446 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

324 ms

js.cookie.min.js

js.cookie.min.js

359 ms

minitekwall.css

minitekwall.css

464 ms

joomla-alert.min.css

joomla-alert.min.css

378 ms

redimstyle.css

redimstyle.css

407 ms

content.min.css

content.min.css

394 ms

style.css

style.css

432 ms

template.css

template.css

1041 ms

global.css

global.css

496 ms

black.css

black.css

516 ms

magnific-popup.css

magnific-popup.css

530 ms

header.css

header.css

540 ms

footer.css

footer.css

578 ms

menu.css

menu.css

612 ms

slider.css

slider.css

637 ms

tabs.css

tabs.css

651 ms

search.css

search.css

650 ms

cookies.css

cookies.css

693 ms

content.css

content.css

844 ms

menu.css

menu.css

759 ms

tables.css

tables.css

758 ms

uslugi.css

uslugi.css

783 ms

images.css

images.css

808 ms

speciality.css

speciality.css

867 ms

news.css

news.css

891 ms

about.css

about.css

905 ms

traditions.css

traditions.css

922 ms

events.css

events.css

959 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

975 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

1133 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

1027 ms

spin.min.js

spin.min.js

1051 ms

core.min.js

core.min.js

1075 ms

messages-es5.min.js

messages-es5.min.js

1083 ms

minitekwall.js

minitekwall.js

1394 ms

menu-es5.min.js

menu-es5.min.js

1149 ms

messages.min.js

messages.min.js

829 ms

accessibility.min.js

accessibility.min.js

952 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

826 ms

buttons.js

buttons.js

864 ms

theme.js

theme.js

862 ms

horisontalScroll.js

horisontalScroll.js

852 ms

steps.js

steps.js

846 ms

stylesheet.css

stylesheet.css

886 ms

stylesheet.css

stylesheet.css

868 ms

speciality.js

speciality.js

871 ms

calculateImageSize.js

calculateImageSize.js

879 ms

full_page_tabs.js

full_page_tabs.js

862 ms

image_zoom.js

image_zoom.js

891 ms

slider.js

slider.js

912 ms

scrollContainer.js

scrollContainer.js

901 ms

logo.svg

logo.svg

110 ms

theme.png

theme.png

132 ms

eye.png

eye.png

160 ms

search.png

search.png

139 ms

slash.png

slash.png

148 ms

arrow.png

arrow.png

193 ms

b-7.webp

b-7.webp

223 ms

a-2.webp

a-2.webp

379 ms

a-1.webp

a-1.webp

379 ms

a-13.webp

a-13.webp

269 ms

b-8.webp

b-8.webp

396 ms

a-2.webp

a-2.webp

318 ms

a-zas.webp

a-zas.webp

440 ms

a-zas.webp

a-zas.webp

388 ms

linkedin.png

linkedin.png

442 ms

vk.png

vk.png

500 ms

facebook.png

facebook.png

510 ms

youtube.png

youtube.png

514 ms

instagram.png

instagram.png

526 ms

telegram.png

telegram.png

548 ms

tik-tok.png

tik-tok.png

571 ms

loader-black.gif

loader-black.gif

582 ms

Gilroy-Regular.woff

Gilroy-Regular.woff

594 ms

Gilroy-Medium.woff

Gilroy-Medium.woff

606 ms

Gilroy-Light.woff

Gilroy-Light.woff

614 ms

Gilroy-UltraLight.woff

Gilroy-UltraLight.woff

625 ms

Gilroy-Thin.woff

Gilroy-Thin.woff

675 ms

Gilroy-Semibold.woff

Gilroy-Semibold.woff

708 ms

Gilroy-Bold.woff

Gilroy-Bold.woff

719 ms

Gilroy-Extrabold.woff

Gilroy-Extrabold.woff

726 ms

Gilroy-Heavy.woff

Gilroy-Heavy.woff

740 ms

Gilroy-Black.woff

Gilroy-Black.woff

750 ms

Montserrat-Regular.woff

Montserrat-Regular.woff

809 ms

Montserrat-Medium.woff

Montserrat-Medium.woff

962 ms

Montserrat-Light.woff

Montserrat-Light.woff

852 ms

Montserrat-ExtraLight.woff

Montserrat-ExtraLight.woff

855 ms

Montserrat-Thin.woff

Montserrat-Thin.woff

915 ms

Montserrat-SemiBold.woff

Montserrat-SemiBold.woff

799 ms

Montserrat-Bold.woff

Montserrat-Bold.woff

854 ms

Montserrat-ExtraBold.woff

Montserrat-ExtraBold.woff

884 ms

Montserrat-Black.woff

Montserrat-Black.woff

875 ms

little_cookie.png

little_cookie.png

852 ms

Accessibility Review

psu.by accessibility score

93

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

psu.by best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

psu.by SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Psu.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 Psu.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

psu.by

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