Tools & Wizards About Us
lexmark.es screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% 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

lexmark.es

Imprima, proteja y gestione su información | Lexmark España (Spain)

Page Load Speed

1.1 sec in total

First Response

52 ms

Resources Loaded

807 ms

Page Rendered

240 ms

lexmark.es screenshot

About Website

Visit lexmark.es now to see the best up-to-date Lexmark content and also check out these interesting facts you probably never knew about lexmark.es

Lexmark crea soluciones y tecnologías de impresión e imagen innovadoras que ayudan a clientes de todo el mundo a imprimir, proteger y gestionar la información con facilidad, eficacia y un valor sin ig...

Visit lexmark.es

Key Findings

We analyzed Lexmark.es page load time and found that the first response time was 52 ms and then it took 1 sec 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.es performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,610 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.168

70/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

es_es.html

52 ms

screen-bs.min.css

69 ms

screen.min.css

61 ms

clientlibs.min.cb878cb20432777f423e96bfec9da6d1.css

5 ms

jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js

37 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lexmark.es, 45% (19 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 (378 ms) relates to the external source Assets.adobedtm.com.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lexmark.es main page is 1.7 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 28.3 kB

  • Original 35.1 kB
  • After minification 27.2 kB
  • After compression 6.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 7.9 kB, which is 22% 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 81% of the original size.

Image Optimization

-1%

Potential reduce by 6.4 kB

  • Original 1.0 MB
  • After minification 996.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. Lexmark images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.6 kB

  • Original 532.2 kB
  • After minification 532.2 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 45 B

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

Requests Breakdown

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

Requests Now

30

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 30 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 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

es_es.html

es_es.html

52 ms

screen-bs.min.css

screen-bs.min.css

69 ms

screen.min.css

screen.min.css

61 ms

clientlibs.min.cb878cb20432777f423e96bfec9da6d1.css

clientlibs.min.cb878cb20432777f423e96bfec9da6d1.css

5 ms

jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js

jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js

37 ms

clientlibs.min.a4d949888106b880feb03fc58bc8445f.js

clientlibs.min.a4d949888106b880feb03fc58bc8445f.js

54 ms

launch-2ff67a58c725.min.js

launch-2ff67a58c725.min.js

378 ms

clientlibs.min.d4e60df2d0b91bef97cd945be42caf8c.css

clientlibs.min.d4e60df2d0b91bef97cd945be42caf8c.css

47 ms

clientlibs.min.851f6a33318bcbeff6041ab3128754be.js

clientlibs.min.851f6a33318bcbeff6041ab3128754be.js

53 ms

dynamicInfo-fefv3.min.js

dynamicInfo-fefv3.min.js

47 ms

typeahead.min.js

typeahead.min.js

46 ms

api.js

api.js

376 ms

utils.min.4a192b590a2c2926fb000264370c0588.js

utils.min.4a192b590a2c2926fb000264370c0588.js

64 ms

granite.min.543d214c88dfa6f4a3233b630c82d875.js

granite.min.543d214c88dfa6f4a3233b630c82d875.js

53 ms

jquery.min.dd9b395c741ce2784096e26619e14910.js

jquery.min.dd9b395c741ce2784096e26619e14910.js

54 ms

apps-bs.min.js

apps-bs.min.js

374 ms

apps.min.js

apps.min.js

63 ms

lexmark-hdwe-printouts-on-table-240208-2560x1440-optimized.jpg

lexmark-hdwe-printouts-on-table-240208-2560x1440-optimized.jpg

133 ms

lexmark-hdwe-a3-family-240208-optimized.png

lexmark-hdwe-a3-family-240208-optimized.png

133 ms

Hero%20Banner_en_us_Success%20Stories_540x270.jpg

Hero%20Banner_en_us_Success%20Stories_540x270.jpg

132 ms

Lexmark-shop-banner_cart-keyboard_540x270.jpg

Lexmark-shop-banner_cart-keyboard_540x270.jpg

122 ms

go-line-business-desktop-printer.png

go-line-business-desktop-printer.png

129 ms

CX825dtpe-printsample.png

CX825dtpe-printsample.png

127 ms

supplies.png

supplies.png

129 ms

lxk-logo-2x.svg

lxk-logo-2x.svg

123 ms

sprite-national-flags-icon-lib.png

sprite-national-flags-icon-lib.png

127 ms

lxk-symbol-2x.svg

lxk-symbol-2x.svg

125 ms

tphero-regular-webfont.woff

tphero-regular-webfont.woff

112 ms

tphero-light-webfont.woff

tphero-light-webfont.woff

111 ms

tphero-medium-webfont.woff

tphero-medium-webfont.woff

112 ms

tphero-semibold-webfont.woff

tphero-semibold-webfont.woff

110 ms

tphero-bold-webfont.woff

tphero-bold-webfont.woff

113 ms

youtube-icon-34x24.png

youtube-icon-34x24.png

112 ms

linkedin-icon-24x24.png

linkedin-icon-24x24.png

113 ms

lexicons.woff

lexicons.woff

45 ms

tphero-regularitalic-webfont.woff

tphero-regularitalic-webfont.woff

45 ms

tphero-lightitalic-webfont.woff

tphero-lightitalic-webfont.woff

46 ms

tphero-mediumitalic-webfont.woff

tphero-mediumitalic-webfont.woff

45 ms

tphero-semibolditalic-webfont.woff

tphero-semibolditalic-webfont.woff

46 ms

tphero-bolditalic-webfont.woff

tphero-bolditalic-webfont.woff

44 ms

recaptcha__en.js

recaptcha__en.js

218 ms

token.json

token.json

182 ms

Accessibility Review

lexmark.es 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

lexmark.es 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

lexmark.es 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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

lexmark.es

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: