Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

lexmark.bg

Print, secure, and manage your information | Lexmark Bulgaria

Page Load Speed

986 ms in total

First Response

34 ms

Resources Loaded

797 ms

Page Rendered

155 ms

lexmark.bg screenshot

About Website

Click here to check amazing Lexmark content. Otherwise, check out these important facts you probably never knew about lexmark.bg

Lexmark създава иновативни технологии и решения за работа с изображения, които помагат на потребителите по целия свят да отпечатват, защитават и управляват информацията с лекота, ефективност и ненадми...

Visit lexmark.bg

Key Findings

We analyzed Lexmark.bg page load time and found that the first response time was 34 ms and then it took 952 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

lexmark.bg performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value2,580 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

bg_bg.html

34 ms

en_bg.html

57 ms

screen-bs.min.css

114 ms

screen.min.css

103 ms

clientlibs.min.cb878cb20432777f423e96bfec9da6d1.css

12 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lexmark.bg, 34% (13 requests) were made to Media.lexmark.com and 3% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (321 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.6 kB (2%)

Content Size

698.2 kB

After Optimization

681.6 kB

In fact, the total size of Lexmark.bg main page is 698.2 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. 40% of websites need less resources to load. Javascripts take 532.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 14.6 kB

  • Original 19.6 kB
  • After minification 16.1 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 3.5 kB, which is 18% 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 14.6 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 512 B

  • Original 12.3 kB
  • After minification 11.8 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. Lexmark images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.5 kB

  • Original 532.0 kB
  • After minification 532.0 kB
  • After compression 530.5 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

-0%

Potential reduce by 25 B

  • Original 134.3 kB
  • After minification 134.3 kB
  • After compression 134.3 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. Lexmark.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (55%)

Requests Now

20

After Optimization

9

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

Accessibility Review

lexmark.bg accessibility score

100

Accessibility Issues

Best Practices

lexmark.bg best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lexmark.bg SEO score

92

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

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexmark.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it does not match the claimed English language. Our system also found out that Lexmark.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 description is not detected on the main page of Lexmark. 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: