2.9 sec in total
119 ms
2.6 sec
174 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 seu dia!
Visit krups.ptWe analyzed Krups.pt page load time and found that the first response time was 119 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
krups.pt performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value22.6 s
0/100
25%
Value9.4 s
12/100
10%
Value1,170 ms
21/100
30%
Value0.042
99/100
15%
Value15.1 s
7/100
10%
119 ms
46 ms
411 ms
361 ms
517 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 72% of them (51 requests) were addressed to the original Krups.pt, 11% (8 requests) were made to Service.force.com and 6% (4 requests) were made to Cdn.tagcommander.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Krups.pt.
Page size can be reduced by 193.5 kB (6%)
3.3 MB
3.1 MB
In fact, the total size of Krups.pt main page is 3.3 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. 65% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 113.0 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.0 kB, which is 12% 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 113.0 kB or 75% of the original size.
Potential reduce by 45.0 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 32.8 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.
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 36 (59%)
61
25
The browser has sent 61 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 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
krups.pt
119 ms
krups.pt
46 ms
www.krups.pt
411 ms
bootstrap.min.css
361 ms
main.min-24.1.css
517 ms
simplePagination.css
296 ms
perfect-scrollbar.css
296 ms
tooltipster.bundle.css
298 ms
js
82 ms
markerclusterer.js
300 ms
tc_Global_SpecificNeeds_89.js
134 ms
tc_header.js
115 ms
tc_Global_analytics_3.js
143 ms
esw.min.js
31 ms
perfect-scrollbar.min.js
618 ms
lazyload.min.js
510 ms
core.min-24.1.js
863 ms
bundle.min-24.1.js
730 ms
wpl.min.js
290 ms
dynamicformsaddon.js
438 ms
gseb.utils.js
723 ms
gseb.richautocomplete.js
617 ms
nicescollv-3.7.6.min.js
1047 ms
product-benefits.js
667 ms
gsebcheckoutaddon.js
833 ms
tc_emarketing.js
117 ms
api.js
11 ms
img-defer-spinner.svg
441 ms
krups-logo-PT
115 ms
Logo-Krups-PT-15Y-picto-header-et-mobile.png
120 ms
img-defer-spinner-small.svg
199 ms
bandeira.jpg
121 ms
01-KRUPS-HP-US-Breakfast-Result-2x.jpg
127 ms
picto-live-chat.png
441 ms
icon-user.png
511 ms
icon-panier.png
514 ms
gotham-book-webfont.woff
656 ms
gotham-black-webfont.woff
413 ms
icomoolinex.woff
510 ms
clock-background.png
406 ms
bg-newsletter.jpg
640 ms
gotham-light-webfont.woff
482 ms
gotham-bold-webfont.woff
784 ms
common.min.js
9 ms
LibreBaskerville-Italic.woff
834 ms
liveagent.esw.min.js
7 ms
jquery.validationEngine.js
200 ms
jquery.validationEngine-pt.js
356 ms
fullpage-krups.js
481 ms
moment-with-locales.min.js
654 ms
home.js
591 ms
close-big.png
391 ms
Banner-1600x484px-2.jpg
401 ms
pequeno-almoco-home.jpg
408 ms
pequeno-almoco-home2.jpg
415 ms
home-pausa.jpg
428 ms
home-pausa-2.jpg
428 ms
orange-pinterest-512-resized.png
429 ms
page.js
81 ms
reach
352 ms
esw.html
19 ms
eswFrame.min.js
55 ms
carousel-arrow-left.png
600 ms
carousel-arrow-right.png
398 ms
session.esw.min.js
35 ms
broadcast.esw.min.js
35 ms
sm.25.html
25 ms
eso.BRQnzO8v.js
39 ms
chasitor.esw.min.js
2 ms
reach
87 ms
print.css
284 ms
krups.pt accessibility score
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-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
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: