Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

omniva.lt

OMNIVA privatiems klientams | omniva.lt

Page Load Speed

4.1 sec in total

First Response

503 ms

Resources Loaded

3.4 sec

Page Rendered

184 ms

About Website

Visit omniva.lt now to see the best up-to-date OMNIVA content for Lithuania and also check out these interesting facts you probably never knew about omniva.lt

OMNIVA siuntų pristatymo paslaugos privatiems klientams. Siųskite ir gaukite siuntas naudodamiesi OMNIVA paštomatais ir kurjerių paslaugomis.

Visit omniva.lt

Key Findings

We analyzed Omniva.lt page load time and found that the first response time was 503 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

omniva.lt performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

omniva.lt

503 ms

www.omniva.lt

793 ms

postprocess.css

102 ms

jquery.bxslider.css

370 ms

typeface.css

513 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 65% of them (32 requests) were addressed to the original Omniva.lt, 6% (3 requests) were made to Static.mailerlite.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (928 ms) belongs to the original domain Omniva.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.0 kB (12%)

Content Size

1.0 MB

After Optimization

910.3 kB

In fact, the total size of Omniva.lt main page is 1.0 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. 55% of websites need less resources to load. Javascripts take 568.5 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 21.3 kB

  • Original 30.5 kB
  • After minification 27.9 kB
  • After compression 9.3 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 21.3 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 392.0 kB
  • After minification 392.0 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. OMNIVA images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 85.9 kB

  • Original 568.5 kB
  • After minification 568.5 kB
  • After compression 482.5 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 85.9 kB or 15% of the original size.

CSS Optimization

-46%

Potential reduce by 22.8 kB

  • Original 49.3 kB
  • After minification 49.3 kB
  • After compression 26.5 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. Omniva.lt needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (69%)

Requests Now

45

After Optimization

14

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

Accessibility Review

omniva.lt accessibility score

59

Accessibility Issues

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

Buttons do not have an accessible name

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

Heading elements are not in a sequentially-descending order

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

omniva.lt 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

omniva.lt SEO score

83

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

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

    LT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omniva.lt can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian 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 Omniva.lt 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 OMNIVA. 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: