Tools & Wizards About Us
md.lexmark.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

md.lexmark.com

Print, secure and manage your information | Lexmark United States

Page Load Speed

688 ms in total

First Response

15 ms

Resources Loaded

512 ms

Page Rendered

161 ms

md.lexmark.com screenshot

About Website

Click here to check amazing Md Lexmark content for Brazil. Otherwise, check out these important facts you probably never knew about md.lexmark.com

Lexmark creates innovative imaging solutions and technologies that help customers worldwide print, secure and manage information with ease, efficiency and unmatched value.

Visit md.lexmark.com

Key Findings

We analyzed Md.lexmark.com page load time and found that the first response time was 15 ms and then it took 673 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

md.lexmark.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

www.lexmark.com

15 ms

www.lexmark.com

20 ms

en_us.html

26 ms

screen-bs.min.css

44 ms

screen.min.css

96 ms

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

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Md.lexmark.com main page is 1.5 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. 70% of websites need less resources to load. Images take 833.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 28.3 kB

  • Original 34.1 kB
  • After minification 25.8 kB
  • After compression 5.8 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 8.4 kB, which is 24% 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 28.3 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 5.4 kB

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

JavaScript Optimization

-0%

Potential reduce by 1.5 kB

  • Original 544.6 kB
  • After minification 544.6 kB
  • After compression 543.1 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 47 B

  • Original 132.3 kB
  • After minification 132.3 kB
  • After compression 132.2 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. Md.lexmark.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

32

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Md 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 13 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.lexmark.com

www.lexmark.com

15 ms

www.lexmark.com

www.lexmark.com

20 ms

en_us.html

en_us.html

26 ms

screen-bs.min.css

screen-bs.min.css

44 ms

screen.min.css

screen.min.css

96 ms

clientlibs.min.cb878cb20432777f423e96bfec9da6d1.css

clientlibs.min.cb878cb20432777f423e96bfec9da6d1.css

6 ms

jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js

jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js

29 ms

clientlibs.min.a4d949888106b880feb03fc58bc8445f.js

clientlibs.min.a4d949888106b880feb03fc58bc8445f.js

33 ms

launch-2ff67a58c725.min.js

launch-2ff67a58c725.min.js

304 ms

clientlibs.min.d4e60df2d0b91bef97cd945be42caf8c.css

clientlibs.min.d4e60df2d0b91bef97cd945be42caf8c.css

34 ms

clientlibs.min.c8722161e34b50ca397509757cffa42b.js

clientlibs.min.c8722161e34b50ca397509757cffa42b.js

41 ms

dynamicInfo-fefv3.min.js

dynamicInfo-fefv3.min.js

31 ms

typeahead.min.js

typeahead.min.js

35 ms

api.js

api.js

305 ms

utils.min.4a192b590a2c2926fb000264370c0588.js

utils.min.4a192b590a2c2926fb000264370c0588.js

33 ms

granite.min.543d214c88dfa6f4a3233b630c82d875.js

granite.min.543d214c88dfa6f4a3233b630c82d875.js

40 ms

jquery.min.dd9b395c741ce2784096e26619e14910.js

jquery.min.dd9b395c741ce2784096e26619e14910.js

36 ms

apps-bs.min.js

apps-bs.min.js

139 ms

apps.min.js

apps.min.js

241 ms

Hero_Banner_Success_Story_1500x600.jpg

Hero_Banner_Success_Story_1500x600.jpg

186 ms

token.json

token.json

189 ms

IoT-green-connected-dots-540x270.jpg

IoT-green-connected-dots-540x270.jpg

184 ms

AI-subanner.jpg

AI-subanner.jpg

187 ms

Lexmark-shop-banner_cart-keyboard_540x270.jpg

Lexmark-shop-banner_cart-keyboard_540x270.jpg

186 ms

go-line-business-desktop-printer.png

go-line-business-desktop-printer.png

184 ms

CX825dtpe-printsample.png

CX825dtpe-printsample.png

183 ms

supplies.png

supplies.png

187 ms

lxk-logo-2x.svg

lxk-logo-2x.svg

180 ms

sprite-national-flags-icon-lib.png

sprite-national-flags-icon-lib.png

182 ms

lxk-symbol-2x.svg

lxk-symbol-2x.svg

186 ms

youtube-white.svg

youtube-white.svg

96 ms

twitter-white.svg

twitter-white.svg

87 ms

linkedin-white.svg

linkedin-white.svg

88 ms

facebook-white.svg

facebook-white.svg

89 ms

tphero-regular-webfont.woff

tphero-regular-webfont.woff

59 ms

tphero-light-webfont.woff

tphero-light-webfont.woff

36 ms

tphero-medium-webfont.woff

tphero-medium-webfont.woff

35 ms

tphero-semibold-webfont.woff

tphero-semibold-webfont.woff

35 ms

tphero-bold-webfont.woff

tphero-bold-webfont.woff

58 ms

lexicons.woff

lexicons.woff

59 ms

tphero-regularitalic-webfont.woff

tphero-regularitalic-webfont.woff

58 ms

tphero-lightitalic-webfont.woff

tphero-lightitalic-webfont.woff

59 ms

tphero-mediumitalic-webfont.woff

tphero-mediumitalic-webfont.woff

59 ms

tphero-semibolditalic-webfont.woff

tphero-semibolditalic-webfont.woff

59 ms

tphero-bolditalic-webfont.woff

tphero-bolditalic-webfont.woff

59 ms

recaptcha__en.js

recaptcha__en.js

63 ms

Accessibility Review

md.lexmark.com accessibility score

90

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

md.lexmark.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

md.lexmark.com SEO score

85

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

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Md.lexmark.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Md.lexmark.com 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

md.lexmark.com

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