Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

interreg.lt

Vandens filtrai geležiai šalinti, nukalkinimui ir ne tik | Geologas.lt

Page Load Speed

5.1 sec in total

First Response

1.4 sec

Resources Loaded

3.4 sec

Page Rendered

311 ms

interreg.lt screenshot

About Website

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

Vandens filtrai – filtrų montavimas ir servisas. Minkštinimas, nugeležinimas, blogų kvapų šalinimas. Vandens tyrimai klientams nemokami.

Visit interreg.lt

Key Findings

We analyzed Interreg.lt page load time and found that the first response time was 1.4 sec and then it took 3.7 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

interreg.lt performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

1443 ms

js

68 ms

css

128 ms

style.min.css

298 ms

embed-public.min.css

419 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Interreg.lt, 10% (4 requests) were made to Static.addtoany.com and 7% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Geologas.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.3 kB (23%)

Content Size

361.5 kB

After Optimization

277.2 kB

In fact, the total size of Interreg.lt main page is 361.5 kB. 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 113.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 74.6 kB

  • Original 97.8 kB
  • After minification 95.4 kB
  • After compression 23.2 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 74.6 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 7.9 kB

  • Original 113.5 kB
  • After minification 105.6 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. Interreg images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 381 B

  • Original 67.2 kB
  • After minification 67.2 kB
  • After compression 66.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.4 kB

  • Original 83.0 kB
  • After minification 83.0 kB
  • After compression 81.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. Interreg.lt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (76%)

Requests Now

37

After Optimization

9

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

Accessibility Review

interreg.lt accessibility score

95

Accessibility Issues

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

interreg.lt best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

interreg.lt SEO score

89

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

    LT

  • Language Claimed

    LT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Interreg.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 Interreg.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 data is detected on the main page of Interreg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: