Tools & Wizards About Us
zynky.lt screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

zynky.lt

Akiniai ir kontaktiniai lęšiai už patrauklią kainą | Zynky optika

Page Load Speed

3.9 sec in total

First Response

174 ms

Resources Loaded

2.2 sec

Page Rendered

1.5 sec

zynky.lt screenshot

About Website

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

Nori susikurti unikalų įvaizdį? Tuomet „Zynky“ akiniai/akinių rėmeliai – kaip tik tau! Nieko nelauk – užsuk ir sužinok apie galimybes daugiau.

Visit zynky.lt

Key Findings

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

Performance Metrics

zynky.lt performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

zynky.lt

174 ms

zynky.lt

55 ms

bricks-advanced-themer.css

21 ms

meta-boxes.css

25 ms

style.css

26 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 82% of them (54 requests) were addressed to the original Zynky.lt, 14% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Go.zynky.lt.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.1 kB (39%)

Content Size

615.9 kB

After Optimization

377.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Zynky.lt main page is 615.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 270.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 232.7 kB

  • Original 270.7 kB
  • After minification 270.6 kB
  • After compression 38.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 232.7 kB or 86% of the original size.

JavaScript Optimization

-0%

Potential reduce by 552 B

  • Original 198.4 kB
  • After minification 198.4 kB
  • After compression 197.8 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

-3%

Potential reduce by 4.8 kB

  • Original 146.8 kB
  • After minification 146.4 kB
  • After compression 142.0 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. Zynky.lt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (94%)

Requests Now

50

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zynky.lt

zynky.lt

174 ms

zynky.lt

zynky.lt

55 ms

bricks-advanced-themer.css

bricks-advanced-themer.css

21 ms

meta-boxes.css

meta-boxes.css

25 ms

style.css

style.css

26 ms

style.min.css

style.min.css

50 ms

frontend.css

frontend.css

35 ms

automatic.css

automatic.css

69 ms

automatic-gutenberg.css

automatic-gutenberg.css

33 ms

css.css

css.css

40 ms

super-speedy-search.css

super-speedy-search.css

37 ms

wpdiscuz-ratings.min.css

wpdiscuz-ratings.min.css

64 ms

frontend.css

frontend.css

54 ms

frontend.min.css

frontend.min.css

56 ms

style.css

style.css

53 ms

woocommerce.min.css

woocommerce.min.css

83 ms

font-awesome-6-brands.min.css

font-awesome-6-brands.min.css

90 ms

ionicons.min.css

ionicons.min.css

91 ms

themify-icons.min.css

themify-icons.min.css

88 ms

automatic-bricks.css

automatic-bricks.css

94 ms

frontend.css

frontend.css

98 ms

css2

css2

110 ms

jquery.min.js

jquery.min.js

99 ms

17389e3519166855e06e3c805a88cfe2.js

17389e3519166855e06e3c805a88cfe2.js

96 ms

5953a4ad05a315868a1256584ff86532.js

5953a4ad05a315868a1256584ff86532.js

96 ms

6a1fbfa9270433522ac00bb3781cd278.js

6a1fbfa9270433522ac00bb3781cd278.js

93 ms

0a4c03f183ef3c21516f967184014eaa.js

0a4c03f183ef3c21516f967184014eaa.js

100 ms

87d8daf56db798cde89898277d961fb8.js

87d8daf56db798cde89898277d961fb8.js

95 ms

de9e2d05165ebb01f1922d715daed783.js

de9e2d05165ebb01f1922d715daed783.js

97 ms

13ed821e90c1a22a81b2f5df05b42333.js

13ed821e90c1a22a81b2f5df05b42333.js

96 ms

9eceed3bffce97160c4469d02e335cb1.js

9eceed3bffce97160c4469d02e335cb1.js

95 ms

4ff3835cd20df19e61a476fe51f68623.js

4ff3835cd20df19e61a476fe51f68623.js

98 ms

547a520d85a87a1e0c58c4463da1ef39.js

547a520d85a87a1e0c58c4463da1ef39.js

99 ms

995d8eaf6ccd160e73b7f3a3446beb62.js

995d8eaf6ccd160e73b7f3a3446beb62.js

99 ms

a3693d430c9b8d758ebecc1238d67536.js

a3693d430c9b8d758ebecc1238d67536.js

101 ms

2d1327f06ee396b702a92919fde50477.js

2d1327f06ee396b702a92919fde50477.js

101 ms

efc76c6ecca0d0ac0c4d21615ebb8c91.js

efc76c6ecca0d0ac0c4d21615ebb8c91.js

99 ms

wc-blocks.css

wc-blocks.css

99 ms

splide.min.css

splide.min.css

93 ms

6dd6ea89c46b3036eedcd6120b2a5925.js

6dd6ea89c46b3036eedcd6120b2a5925.js

95 ms

d668cabedf6ce5936a745d84890be3e2.js

d668cabedf6ce5936a745d84890be3e2.js

91 ms

ab21247dded1a4da4e4692dbc2e1c830.js

ab21247dded1a4da4e4692dbc2e1c830.js

91 ms

38c00cfdf7160d4b56777980c7241da3.js

38c00cfdf7160d4b56777980c7241da3.js

230 ms

0c867bfb071536a0fdff7663df610d6d.js

0c867bfb071536a0fdff7663df610d6d.js

228 ms

3e1f30e463d441267290563c4d9d3e00.js

3e1f30e463d441267290563c4d9d3e00.js

229 ms

842d5eb4bf0aed79439e4d10d822572b.js

842d5eb4bf0aed79439e4d10d822572b.js

217 ms

e7f5b68dfa8ff61c68fe8e8351fe8ed2.js

e7f5b68dfa8ff61c68fe8e8351fe8ed2.js

213 ms

5d0dd1005ea9662d0fc78432b534f401.js

5d0dd1005ea9662d0fc78432b534f401.js

213 ms

a9564bd8cb389a4284e791725c64b1b9.js

a9564bd8cb389a4284e791725c64b1b9.js

206 ms

6901704642a18701fc4447d114a4321c.js

6901704642a18701fc4447d114a4321c.js

205 ms

gtm.js

gtm.js

372 ms

zynkylogo_white_web-1024x169.png

zynkylogo_white_web-1024x169.png

1822 ms

zynkylogo_white_web-1.svg

zynkylogo_white_web-1.svg

109 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

153 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

218 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

247 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

250 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

248 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

249 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

248 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

247 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

247 ms

themify.woff

themify.woff

55 ms

fa-brands-400.ttf

fa-brands-400.ttf

678 ms

ionicons.woff

ionicons.woff

566 ms

wpi-sss-icons.woff

wpi-sss-icons.woff

365 ms

Accessibility Review

zynky.lt accessibility score

85

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

zynky.lt SEO score

93

Search Engine Optimization Advices

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

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

zynky.lt

Open Graph data is detected on the main page of Zynky. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: