Tools & Wizards About Us
oi.ut.ee screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

oi.ut.ee

TÜ õigusteaduskond | Tartu Ülikool

Page Load Speed

7.1 sec in total

First Response

364 ms

Resources Loaded

6.5 sec

Page Rendered

249 ms

oi.ut.ee screenshot

About Website

Visit oi.ut.ee now to see the best up-to-date Oi Ut content for Estonia and also check out these interesting facts you probably never knew about oi.ut.ee

Tartu Ülikool on Baltimaade juhtiv ülikool, kuuludes ainukesena regioonis maailma 1,2% parima sekka. TÜ maailmatasemel haridus annab eelise kogu eluks!

Visit oi.ut.ee

Key Findings

We analyzed Oi.ut.ee page load time and found that the first response time was 364 ms and then it took 6.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

oi.ut.ee performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

oi.ut.ee

364 ms

et

2679 ms

css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css

1546 ms

css_07J8x41x2O5KaYV9_sY-M_y1fm8-6LmJytIRAax1oDY.css

1881 ms

css_YgSfqHCg9vs7VGk2xZqfcX1CD-Ter7Bhd7fQkJWsCkI.css

1976 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 81% of them (42 requests) were addressed to the original Oi.ut.ee, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Oi.ut.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 873.5 kB (51%)

Content Size

1.7 MB

After Optimization

839.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oi.ut.ee main page is 1.7 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. Images take 699.5 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 252.7 kB

  • Original 277.3 kB
  • After minification 253.2 kB
  • After compression 24.6 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 252.7 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 38.2 kB

  • Original 699.5 kB
  • After minification 661.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. Oi Ut images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 420.4 kB

  • Original 537.2 kB
  • After minification 374.4 kB
  • After compression 116.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 420.4 kB or 78% of the original size.

CSS Optimization

-82%

Potential reduce by 162.2 kB

  • Original 199.0 kB
  • After minification 194.2 kB
  • After compression 36.8 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. Oi.ut.ee needs all CSS files to be minified and compressed as it can save up to 162.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (61%)

Requests Now

49

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oi.ut.ee

oi.ut.ee

364 ms

et

et

2679 ms

css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css

css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css

1546 ms

css_07J8x41x2O5KaYV9_sY-M_y1fm8-6LmJytIRAax1oDY.css

css_07J8x41x2O5KaYV9_sY-M_y1fm8-6LmJytIRAax1oDY.css

1881 ms

css_YgSfqHCg9vs7VGk2xZqfcX1CD-Ter7Bhd7fQkJWsCkI.css

css_YgSfqHCg9vs7VGk2xZqfcX1CD-Ter7Bhd7fQkJWsCkI.css

1976 ms

css_88zsqhgEK5S9VE9VcziaucXaenFL3Rck9S_m0YRJIo4.css

css_88zsqhgEK5S9VE9VcziaucXaenFL3Rck9S_m0YRJIo4.css

2095 ms

css_Xscaplabf8BB3-nYnPGx7pSBwvjLPOrD5-ypESKuYCM.css

css_Xscaplabf8BB3-nYnPGx7pSBwvjLPOrD5-ypESKuYCM.css

2130 ms

js_zzcIWOou_jnX0ZWAIA4sb6Xy_p5a8FZNA0GySvuWjPU.js

js_zzcIWOou_jnX0ZWAIA4sb6Xy_p5a8FZNA0GySvuWjPU.js

848 ms

js_JoT-jBF0JuucG5UKr6UZr8omEDVGPq-DJ0xFzISjUAs.js

js_JoT-jBF0JuucG5UKr6UZr8omEDVGPq-DJ0xFzISjUAs.js

973 ms

js_B_7xv70S_0JCHRPIVyb6fns3Eu-cMkRsaE5tiHFtDcc.js

js_B_7xv70S_0JCHRPIVyb6fns3Eu-cMkRsaE5tiHFtDcc.js

1096 ms

js_VBG8PDWxrMbKVKcqqFY1YSA5TLhrYD7WnHOkctmmYGw.js

js_VBG8PDWxrMbKVKcqqFY1YSA5TLhrYD7WnHOkctmmYGw.js

1222 ms

js_4Jy4AcerRr0bz-t11R8efOO-0AMz7X6zs01LYAkxlxk.js

js_4Jy4AcerRr0bz-t11R8efOO-0AMz7X6zs01LYAkxlxk.js

1345 ms

js_ra4GSh9XLawx5USZ8Oc43FPoJBY9ybxvo6rldtvizqI.js

js_ra4GSh9XLawx5USZ8Oc43FPoJBY9ybxvo6rldtvizqI.js

1469 ms

js_uwrfBOJCFVq42muTMjrq2bD-RUh8NNq_fZRTb6dsNb4.js

js_uwrfBOJCFVq42muTMjrq2bD-RUh8NNq_fZRTb6dsNb4.js

1592 ms

js_6TXWonmdGlHMZQoqfjGfgGcyCroYL3xUcsnE1scqP2g.js

js_6TXWonmdGlHMZQoqfjGfgGcyCroYL3xUcsnE1scqP2g.js

940 ms

css

css

23 ms

ga.js

ga.js

220 ms

body_bg.jpg

body_bg.jpg

180 ms

toolbar_grad.png

toolbar_grad.png

177 ms

header_sprite.png

header_sprite.png

175 ms

logo_oi_et.png

logo_oi_et.png

176 ms

vis-imp-button.png

vis-imp-button.png

176 ms

header_selection_bg.png

header_selection_bg.png

273 ms

faculties_select_bg.png

faculties_select_bg.png

274 ms

top_menu_bg.png

top_menu_bg.png

273 ms

mainmenu-border.png

mainmenu-border.png

273 ms

content_footer_bg.jpg

content_footer_bg.jpg

276 ms

slider-bullets-bg.png

slider-bullets-bg.png

276 ms

slider-bullets.png

slider-bullets.png

370 ms

ulle_madise.jpg

ulle_madise.jpg

828 ms

lahtisteustepaev.jpg

lahtisteustepaev.jpg

728 ms

ut140904at035.jpg

ut140904at035.jpg

713 ms

slaider_7_3.jpg

slaider_7_3.jpg

620 ms

tu_dj_koduleht_slider_620x345_est_loplik_0.jpg

tu_dj_koduleht_slider_620x345_est_loplik_0.jpg

862 ms

pattern_alpha_5.png

pattern_alpha_5.png

485 ms

listbullet.png

listbullet.png

601 ms

it-law-videopaeis-01_0.png

it-law-videopaeis-01_0.png

945 ms

menu-collapsed.png

menu-collapsed.png

742 ms

boxheading-ribbon-tailmask.png

boxheading-ribbon-tailmask.png

828 ms

h2_sprite.png

h2_sprite.png

847 ms

pattern_alpha_3.png

pattern_alpha_3.png

874 ms

footer-border.png

footer-border.png

942 ms

all.js

all.js

150 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

102 ms

message-24-error.png

message-24-error.png

775 ms

__utm.gif

__utm.gif

29 ms

172 ms

xd_arbiter.php

xd_arbiter.php

49 ms

xd_arbiter.php

xd_arbiter.php

69 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

34 ms

blank.png

blank.png

125 ms

ping

ping

94 ms

Accessibility Review

oi.ut.ee accessibility score

93

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Best Practices

oi.ut.ee best practices score

92

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

SEO Factors

oi.ut.ee SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ET

  • Language Claimed

    ET

  • Encoding

    UTF-8

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

oi.ut.ee

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