6.5 sec in total
104 ms
6.1 sec
313 ms
Visit lexmark.pt now to see the best up-to-date Lexmark content and also check out these interesting facts you probably never knew about lexmark.pt
A Lexmark cria soluções e tecnologias de impressão inovadoras que ajudam os nossos clientes em todo o mundo a imprimirem, protegerem e gerirem informações com facilidade e eficiência, com uma rentabil...
Visit lexmark.ptWe analyzed Lexmark.pt page load time and found that the first response time was 104 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lexmark.pt performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value18.9 s
0/100
25%
Value7.7 s
24/100
10%
Value690 ms
43/100
30%
Value0.076
95/100
15%
Value13.0 s
13/100
10%
104 ms
119 ms
52 ms
16 ms
22 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lexmark.pt, 82% (65 requests) were made to Lexmark.com and 5% (4 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source S1411.t.eloqua.com.
Page size can be reduced by 1.4 MB (73%)
1.9 MB
519.0 kB
In fact, the total size of Lexmark.pt main page is 1.9 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. 60% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 42.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. This page needs HTML code to be minified as it can gain 10.7 kB, which is 21% 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 42.9 kB or 86% of the original size.
Potential reduce by 25.1 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. Obviously, Lexmark needs image optimization as it can save up to 25.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 773.7 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 773.7 kB or 70% of the original size.
Potential reduce by 550.0 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.pt needs all CSS files to be minified and compressed as it can save up to 550.0 kB or 92% of the original size.
Number of requests can be reduced by 56 (81%)
69
13
The browser has sent 69 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 53 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lexmark.pt
104 ms
119 ms
pt_pt.html
52 ms
clientlibs.min.css
16 ms
jquery.min.js
22 ms
utils.min.js
20 ms
granite.min.js
18 ms
jquery.min.js
18 ms
clientlibs.min.js
60 ms
satelliteLib-73facede7bc51e73160930494286ce4ba258a138.js
162 ms
lxk-framework.css
131 ms
pagination.css
34 ms
utilities.css
36 ms
require.js
106 ms
main.js
107 ms
jwplayer.js
121 ms
header-footer.css
145 ms
mbox.js
149 ms
shared.min.js
154 ms
underscore.min.js
154 ms
kernel.min.js
231 ms
analytics.js
75 ms
target.js
140 ms
standard
41 ms
tracker.js
35 ms
modernizr-2.6.3.js
36 ms
jquery-private.js
33 ms
collect
36 ms
s_code.js
29 ms
tracker-presets.js
27 ms
jquery-1.10.2.min.js
29 ms
sc-map.js
18 ms
1453727810600.jpg
26 ms
lxk-logo-2x.png
28 ms
sprite-ui-icon-lib.png
29 ms
sprite-national-flags-icon-lib-12.png
27 ms
tphero-regular-webfont.woff
603 ms
tphero-light-webfont.woff
605 ms
tphero-medium-webfont.woff
609 ms
tphero-semibold-webfont.woff
607 ms
tphero-bold-webfont.woff
609 ms
lxk-ui.woff
602 ms
header-footer.js
592 ms
search.js
592 ms
lxk-symbol-2x.png
559 ms
satellite-56ab961164746d0a7c001726.js
64 ms
satellite-55e891e36466340017000e55.js
549 ms
s-code-contents-dea945c1d332ada2f6d65951bf6980fe95c50e1a.js
549 ms
scookie
2263 ms
elqCfg.min.js
109 ms
breadcrumb.js
57 ms
custom-input.js
49 ms
form-selectbox.js
50 ms
responsive-tables.js
54 ms
set.js
49 ms
modal.js
107 ms
modalmanager.js
92 ms
responsive-images.js
92 ms
dropdown.js
133 ms
slide-in-panel.js
94 ms
carousel.js
144 ms
alerts.js
142 ms
quote.js
145 ms
rail-nav.js
160 ms
griddy.js
162 ms
card.js
174 ms
sifter.js
171 ms
form.js
174 ms
banner.js
184 ms
modal.js
186 ms
pagination.js
191 ms
jquery.ba-throttle-debounce.js
143 ms
svrGP
4509 ms
CS820-launch-banner-desktop-option2.jpg
214 ms
media-queries.js
142 ms
s73812576427590
135 ms
variables.js
128 ms
s78643329860642
100 ms
svrGP.aspx
186 ms
lexmark.pt accessibility score
lexmark.pt 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.pt SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexmark.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Lexmark.pt 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.pt
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: