Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

aurika.lt

Lipnių etikečių ir lanksčių pakuočių gamintojai - Aurika

Page Load Speed

7.7 sec in total

First Response

977 ms

Resources Loaded

5.9 sec

Page Rendered

814 ms

aurika.lt screenshot

About Website

Click here to check amazing Aurika content for Lithuania. Otherwise, check out these important facts you probably never knew about aurika.lt

Lanksčios pakuotės ir etikečių gamyba yra mūsų darbas, kurį atlikdami sujungiame ilgametę patirtį su novatoriškomis idėjomis. Dirbant kartu, Jums nereikės išmanyti pakuotės, o ją įsigyti gali tapti pa...

Visit aurika.lt

Key Findings

We analyzed Aurika.lt page load time and found that the first response time was 977 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

aurika.lt performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,970 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

www.aurika.lt

977 ms

main.css

602 ms

jquery.fancybox.css

237 ms

all.min.js

1165 ms

ga_helpers.js

246 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 96% of them (45 requests) were addressed to the original Aurika.lt, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Aurika.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (31%)

Content Size

4.2 MB

After Optimization

2.9 MB

In fact, the total size of Aurika.lt main page is 4.2 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 140.6 kB

  • Original 156.5 kB
  • After minification 156.0 kB
  • After compression 15.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 140.6 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 158.0 kB

  • Original 2.7 MB
  • After minification 2.5 MB

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. Aurika images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 633.4 kB

  • Original 922.1 kB
  • After minification 922.1 kB
  • After compression 288.7 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 633.4 kB or 69% of the original size.

CSS Optimization

-90%

Potential reduce by 373.0 kB

  • Original 413.3 kB
  • After minification 297.5 kB
  • After compression 40.3 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. Aurika.lt needs all CSS files to be minified and compressed as it can save up to 373.0 kB or 90% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

41

After Optimization

41

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aurika. According to our analytics all requests are already optimized.

Accessibility Review

aurika.lt accessibility score

72

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

button, link, and menuitem elements do not have accessible names.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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

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

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

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

aurika.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

aurika.lt SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    LT

  • Language Claimed

    LT

  • Encoding

    UTF-8

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