27.4 sec in total
69 ms
18.7 sec
8.6 sec
Visit lexmark.com now to see the best up-to-date Lexmark content for Brazil and also check out these interesting facts you probably never knew about 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 lexmark.comWe analyzed Lexmark.com page load time and found that the first response time was 69 ms and then it took 27.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
lexmark.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value12.9 s
0/100
25%
Value9.3 s
12/100
10%
Value6,740 ms
0/100
30%
Value0.177
68/100
15%
Value15.8 s
6/100
10%
69 ms
63 ms
12 ms
223 ms
1224 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 29% of them (20 requests) were addressed to the original Lexmark.com, 28% (19 requests) were made to Media.lexmark.com and 14% (10 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Lexmark.com.
Page size can be reduced by 2.5 MB (62%)
4.0 MB
1.5 MB
In fact, the total size of Lexmark.com main page is 4.0 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 25.4 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.4 kB, which is 23% 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 25.4 kB or 80% of the original size.
Potential reduce by 50.4 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.
Potential reduce by 1.1 MB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.1 MB or 70% of the original size.
Potential reduce by 1.3 MB
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.com needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 90% of the original size.
Number of requests can be reduced by 38 (69%)
55
17
The browser has sent 55 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 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
lexmark.com
69 ms
www.lexmark.com
63 ms
12 ms
en_us.html
223 ms
satelliteLib-73facede7bc51e73160930494286ce4ba258a138.js
1224 ms
bootstrap.min.css
2727 ms
screen.min.css
2683 ms
screen.min.css
1091 ms
jwplayer.js
204 ms
clientlibs.min.css
204 ms
jquery.min.js
342 ms
clientlibs.min.js
204 ms
dynamicInfo-fefv3.js
355 ms
utils.min.js
354 ms
granite.min.js
354 ms
jquery.min.js
339 ms
bootstrap.min.js
2748 ms
apps.min.js
2380 ms
apps.min.js
1918 ms
id
1104 ms
mbox-contents-eb5a39f4a23f6e84b47fe357302130f9e5b482c9.js
139 ms
satellite-57daa0e364746d361900fbb5.js
920 ms
satellite-5887b01d64746d6237000dca.js
919 ms
analytics.js
876 ms
target.js
1408 ms
id
4380 ms
collect
4663 ms
jquery-1.10.2.min.js
5153 ms
ibs:dpid=411&dpuuid=Wa68vAAAA4RaPA2j
1833 ms
ajax
2932 ms
2840.js
2581 ms
collect
2199 ms
lxk-logo-2x.svg
1023 ms
A3-family-shot-black-expanded-2000x540.jpg
1417 ms
b3-green3.png
1017 ms
HomePage_whiteShots_CS720.png
1301 ms
CX825dtpe-printsample.png
1233 ms
supplies.png
1302 ms
Flat_National-Flags_Sprite-12px.png
1302 ms
lxk-symbol-2x.svg
1016 ms
dest5.html
1092 ms
tphero-regular-webfont.ttf
1209 ms
tphero-light-webfont.ttf
843 ms
tphero-medium-webfont.ttf
1887 ms
tphero-semibold-webfont.ttf
2003 ms
tphero-bold-webfont.ttf
1972 ms
lxk-ui.ttf
1971 ms
lexmark_iss_icon_font.ttf
2046 ms
youtube-icon-34x24.png
1157 ms
twitter-icon-30x24.png
1157 ms
linkedin-icon-24x24.png
1232 ms
facebook-icon-24x24.png
1123 ms
in-context-icon-34x24.png
1123 ms
satellite-56ab961164746d0a7c001726.js
949 ms
p-XQLqCyH2p7U6R.gif
1006 ms
satellite-573ddfc764746d2dff00697b.js
946 ms
satellite-55e891e36466340017000e55.js
948 ms
satellite-5810e6cc64746d7de000b558.js
948 ms
satellite-582dd65b64746d064b005028.js
947 ms
s-code-contents-dea945c1d332ada2f6d65951bf6980fe95c50e1a.js
873 ms
aquant.js
317 ms
s75017185893375
50 ms
pixel;r=661756801;labels=_fp.event.Lexmark%20Homepage;rf=3;a=p-XQLqCyH2p7U6R;url=http%3A%2F%2Fwww.lexmark.com%2Fen_us.html;fpan=1;fpa=P0-867150324-1504623815708;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504623815708;tzo=-180;ogl=url.http%3A%2F%2Fwww%252Elexmark%252Ecom%2Fen_us%252Ehtml%2Ctype.article
1459 ms
token.json
3257 ms
914 ms
dynamicInfoJSON.jsp
893 ms
s
606 ms
elqCfg.min.js
566 ms
u
533 ms
lexmark.com accessibility score
lexmark.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lexmark.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
lexmark.com
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: