Access ru.lv. Rēzeknes Tehnoloģiju akadēmija – Tavs staRTA punkts RĒZEKNĒ!

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value42.5 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.37

29/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

ru.lv

883 ms

structure.css

489 ms

sidemenu.css

487 ms

mainmenu.css

490 ms

navigation.css

491 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 88% of them (75 requests) were addressed to the original Ru.lv, 4% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ru.lv.

Content Size

1.6 MB

After Optimization

753.6 kB

In fact, the total size of Ru.lv main page is 1.6 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. 35% of websites need less resources to load. Images take 711.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 94.3 kB

Original 108.1 kB
After minification 60.8 kB
After compression 13.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. This page needs HTML code to be minified as it can gain 47.3 kB, which is 44% 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 94.3 kB or 87% of the original size.

Image Optimization

-21%

Potential reduce by 151.5 kB

Original 711.5 kB
After minification 560.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. Obviously, Ru needs image optimization as it can save up to 151.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 422.5 kB

Original 553.5 kB
After minification 405.7 kB
After compression 131.1 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 422.5 kB or 76% of the original size.

CSS Optimization

-82%

Potential reduce by 227.9 kB

Original 276.4 kB
After minification 268.6 kB
After compression 48.6 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. Ru.lv needs all CSS files to be minified and compressed as it can save up to 227.9 kB or 82% of the original size.

Requests Now

After Optimization

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ru. 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 13 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

robots.txt is not valid

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

LV
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ru.lv can be misinterpreted by Google and other search engines. Our service has detected that Latvian/Lettish 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 Ru.lv 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

ru.lv

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Rēzeknes Tehnoloģiju akadēmija – Tavs staRTA punkts RĒZEKNĒ!

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ru.lv

structure.css

sidemenu.css

mainmenu.css

navigation.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ru.lv

structure.css

sidemenu.css

mainmenu.css

navigation.css

content.css

controls.css

media_queries.css

css

respond.src.js

modernizr.custom.js

jquery-1.10.2.js

ad_slider.css

bjqs.css

demo.css

bjqs-1.3.min.js

html.css

jquery.fancybox.css

jquery.fancybox.js

jquery.fancybox-media.js

cbpHorizontalMenu.min.js

0.jpg

jxtJU4MACYo

grid.png

header_left.png

new_header_backgorund_980.png

rtalogo.png

icon_lock.png

lv.png

en.png

icon-search.png

triangle_orange.png

breadcrumb_nav.png

navbit-home.png

squares.png

sidemenu_bottom_shadow.png

sidemenu_bullet.png

inzenieru_fak_virtuala_ture.jpg

mic.jpg

karjera_rta.jpg

Fotogalerija.gif

Dialogi_baneris.gif

atv.jpg