5.1 sec in total
311 ms
4.3 sec
490 ms
Visit krups.pt now to see the best up-to-date Krups content for Portugal and also check out these interesting facts you probably never knew about krups.pt
Descubra os pequenos eletrodomésticos Krups, máquinas de café expresso e gamas de pequeno-almço! A melhor forma de começar o dia!
Visit krups.ptWe analyzed Krups.pt page load time and found that the first response time was 311 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
krups.pt performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value22.7 s
0/100
25%
Value20.1 s
0/100
10%
Value19,960 ms
0/100
30%
Value0.042
99/100
15%
Value31.3 s
0/100
10%
311 ms
630 ms
381 ms
515 ms
294 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 68% of them (51 requests) were addressed to the original Krups.pt, 11% (8 requests) were made to Service.force.com and 5% (4 requests) were made to Cdn.tagcommander.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Krups.pt.
Page size can be reduced by 289.8 kB (10%)
2.8 MB
2.5 MB
In fact, the total size of Krups.pt main page is 2.8 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. 85% 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 2.2 MB which makes up the majority of the site volume.
Potential reduce by 96.3 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 18.8 kB, which is 15% 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 96.3 kB or 77% of the original size.
Potential reduce by 157.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. Krups images are well optimized though.
Potential reduce by 33.0 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 33.0 kB or 12% of the original size.
Potential reduce by 2.7 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. Krups.pt has all CSS files already compressed.
Number of requests can be reduced by 39 (59%)
66
27
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krups. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
krups.pt
311 ms
www.krups.pt
630 ms
bootstrap.min.css
381 ms
main.min-22.4.1.css
515 ms
simplePagination.css
294 ms
perfect-scrollbar.css
292 ms
tooltipster.bundle.css
295 ms
js
101 ms
markerclusterer.js
176 ms
tc_Global_SpecificNeeds_89.js
237 ms
tc_header.js
241 ms
tc_Global_analytics_3.js
242 ms
esw.min.js
153 ms
perfect-scrollbar.min.js
375 ms
lazyload.min.js
716 ms
core.min-22.4.1.js
798 ms
bundle.min-22.4.1.js
719 ms
api.js
170 ms
wpl.min.js
165 ms
dynamicformsaddon.js
716 ms
gseb.utils.js
714 ms
gseb.richautocomplete.js
790 ms
nicescollv-3.7.6.min.js
814 ms
product-benefits.js
715 ms
gsebcheckoutaddon.js
716 ms
tc_emarketing.js
172 ms
gen_204
83 ms
img-defer-spinner.svg
105 ms
krups-logo-PT
32 ms
Logo-Krups-PT-15Y-picto-header-et-mobile.png
34 ms
img-defer-spinner-small.svg
105 ms
Krups-picto-contact.png
93 ms
bandeira.jpg
101 ms
01-KRUPS-HP-US-Breakfast-Result-2x.jpg
102 ms
picto-live-chat.png
643 ms
icon-user.png
106 ms
gotham-book-webfont.woff
534 ms
gotham-black-webfont.woff
530 ms
icomoolinex.woff
522 ms
icon-panier.png
86 ms
clock-background.png
489 ms
gotham-light-webfont.woff
443 ms
gotham-bold-webfont.woff
593 ms
bg-newsletter.jpg
443 ms
common.min.js
392 ms
jquery.validationEngine.js
321 ms
jquery.validationEngine-pt.js
176 ms
fullpage-krups.js
181 ms
moment-with-locales.min.js
325 ms
home.js
460 ms
page.js
293 ms
reach
559 ms
close-big.png
218 ms
BANNER-KRUPS-1600x484-05.png
314 ms
pequeno-almoco-home.jpg
316 ms
pequeno-almoco-home2.jpg
1031 ms
home-pausa.jpg
317 ms
home-pausa-2.jpg
1496 ms
orange-pinterest-512-resized.png
314 ms
LibreBaskerville-Italic.woff
269 ms
carousel-arrow-left.png
103 ms
carousel-arrow-right.png
102 ms
recaptcha__pt.js
94 ms
liveagent.esw.min.js
56 ms
eso.e18d3993.js
61 ms
sm.23.html
86 ms
reach
89 ms
print.css
279 ms
nr-spa-1216.min.js
42 ms
esw.html
11 ms
eswFrame.min.js
27 ms
517787514b
153 ms
session.esw.min.js
22 ms
broadcast.esw.min.js
18 ms
chasitor.esw.min.js
20 ms
krups.pt accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
krups.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
Page has valid source maps
krups.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Krups.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 Krups.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.
krups.pt
Open Graph description is not detected on the main page of Krups. 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: