Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

pocius.lt

Advokatas Zigmas Pocius | Advokatų kontora

Page Load Speed

444 ms in total

First Response

160 ms

Resources Loaded

171 ms

Page Rendered

113 ms

pocius.lt screenshot

About Website

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

Advokatas Zigmas Pocius dirbo Klaipėdos apygardos teismo baudžiamųjų bylų skyriaus teisėju ir dabar teikia teisinę pagalbą. Susisiekite: Tel. +370 6 868 52 36; +370 4 631 40 25, el. paštas: zigmas@poc...

Visit pocius.lt

Key Findings

We analyzed Pocius.lt page load time and found that the first response time was 160 ms and then it took 284 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

pocius.lt performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value6.7 s

35/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

pocius.lt

160 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Pocius.lt and no external sources were called. The less responsive or slowest element that took the longest time to load (160 ms) belongs to the original domain Pocius.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 51 B (27%)

Content Size

186 B

After Optimization

135 B

In fact, the total size of Pocius.lt main page is 186 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 186 B which makes up the majority of the site volume.

HTML Optimization

-27%

Potential reduce by 51 B

  • Original 186 B
  • After minification 166 B
  • After compression 135 B

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 20 B, which is 11% 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 51 B or 27% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

pocius.lt accessibility score

64

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

[aria-*] attributes do not match their roles

High

[role]s do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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.

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

Links do not have a discernible name

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

pocius.lt best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pocius.lt SEO score

92

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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