Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

vulcan.lt

Sportinė Apranga ir Treningai nuo 2006 m. Vulcan.lt

Page Load Speed

8.2 sec in total

First Response

525 ms

Resources Loaded

7.3 sec

Page Rendered

386 ms

vulcan.lt screenshot

About Website

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

ADIDAS® NIKE® PUMA® Sportinė Apranga ir Treningai Internetu. IŠPARDAVIMAI kasdien. ✅15m PATIRTIS. Apsipirkite ✅DABAR su NEMOKAMU pristatymu ir GARANTIJOMIS.

Visit vulcan.lt

Key Findings

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

Performance Metrics

vulcan.lt performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

vulcan.lt

525 ms

www.vulcan.lt

1637 ms

common.js

267 ms

browser_identificator.js

269 ms

css

24 ms

Our browser made a total of 132 requests to load all elements on the main page. We found that 74% of them (98 requests) were addressed to the original Vulcan.lt, 7% (9 requests) were made to Trackers.adtarget.me and 5% (6 requests) were made to Litatex.mailerlite.lt. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Vulcan.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 468.3 kB (43%)

Content Size

1.1 MB

After Optimization

632.8 kB

In fact, the total size of Vulcan.lt main page is 1.1 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. 45% of websites need less resources to load. Images take 540.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 117.2 kB

  • Original 134.2 kB
  • After minification 101.9 kB
  • After compression 16.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 32.3 kB, which is 24% 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 117.2 kB or 87% of the original size.

Image Optimization

-8%

Potential reduce by 40.7 kB

  • Original 540.1 kB
  • After minification 499.4 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. Vulcan images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 88.7 kB

  • Original 166.6 kB
  • After minification 151.5 kB
  • After compression 77.9 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 88.7 kB or 53% of the original size.

CSS Optimization

-85%

Potential reduce by 221.6 kB

  • Original 260.2 kB
  • After minification 212.6 kB
  • After compression 38.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. Vulcan.lt needs all CSS files to be minified and compressed as it can save up to 221.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (40%)

Requests Now

125

After Optimization

75

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

Accessibility Review

vulcan.lt accessibility score

69

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

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

vulcan.lt best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

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

    EN

  • Encoding

    UTF-8

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