Tools & Wizards About Us

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

st-petka-eyeclinic.bg

Очна клиника Света Петка град Варна - очни заболявания

Page Load Speed

4.3 sec in total

First Response

542 ms

Resources Loaded

3.1 sec

Page Rendered

602 ms

About Website

Welcome to st-petka-eyeclinic.bg homepage info - get ready to check St Petka Eyeclinic best content for Bulgaria right away, or after learning these important things about st-petka-eyeclinic.bg

Очна клиника Света Петка е открита на 5.5.2000г. от доц. д-р Тошо Митов. Лекуваме Глаукома, мътнини, сухо око, амблиопиа, катаракта и други очни заболявани

Visit st-petka-eyeclinic.bg

Key Findings

We analyzed St-petka-eyeclinic.bg page load time and found that the first response time was 542 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

st-petka-eyeclinic.bg performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

st-petka-eyeclinic.bg

542 ms

st-petka-eyeclinic.bg

735 ms

jquery-ui.css

340 ms

font-awesome.css

341 ms

style.css

353 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 72% of them (67 requests) were addressed to the original St-petka-eyeclinic.bg, 26% (24 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain St-petka-eyeclinic.bg.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

857.4 kB

  • HTML
  • Images

In fact, the total size of St-petka-eyeclinic.bg 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. 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. Images take 813.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 250.3 kB

  • Original 301.1 kB
  • After minification 294.1 kB
  • After compression 50.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. 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 250.3 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 6.5 kB

  • Original 813.0 kB
  • After minification 806.5 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. St Petka Eyeclinic images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 41 (65%)

Requests Now

63

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

st-petka-eyeclinic.bg accessibility score

87

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

st-petka-eyeclinic.bg best practices score

92

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

SEO Factors

st-petka-eyeclinic.bg SEO score

100

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

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise St-petka-eyeclinic.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that St-petka-eyeclinic.bg 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 St Petka Eyeclinic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: