Access e-pacientas.lt. e-Pacientas.lt - Jūsų sveikatos informacijos portalas

name

value

score

weighting

FCP (First Contentful Paint)

Value14.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value1,460 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

e-pacientas.lt

474 ms

css

32 ms

scripts.8cd3c5059dd14741.js

231 ms

styles.f0b64f0ea2f1aa66.css

576 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original E-pacientas.lt, 25% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (576 ms) belongs to the original domain E-pacientas.lt.

Content Size

4.9 kB

After Optimization

2.0 kB

In fact, the total size of E-pacientas.lt main page is 4.9 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. Only 5% of websites need less resources to load. HTML takes 4.9 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 2.9 kB

Original 4.9 kB
After minification 4.9 kB
After compression 2.0 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 2.9 kB or 59% of the original size.

Requests Now

After Optimization

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

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

Form elements do not have associated labels

These are opportunities to improve the legibility of your content.

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

High

robots.txt is not valid

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

LT
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-pacientas.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 E-pacientas.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

e-pacientas.lt

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