23.1 sec in total
100 ms
22.6 sec
366 ms
Welcome to lindt.com.br homepage info - get ready to check Lindt best content for Brazil right away, or after learning these important things about lindt.com.br
Na Lindt Brasil você pode fazer seu pedido pela internet e receber seus chocolates deliciosos em casa. Descubra o mundo do chocolate com a Lindt Sprungli.
Visit lindt.com.brWe analyzed Lindt.com.br page load time and found that the first response time was 100 ms and then it took 23 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lindt.com.br performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value29.2 s
0/100
25%
Value23.1 s
0/100
10%
Value2,710 ms
3/100
30%
Value0.729
6/100
15%
Value29.5 s
0/100
10%
100 ms
2820 ms
56 ms
66 ms
101 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Lindt.com.br, 91% (136 requests) were made to Static-master.shop.lindt.com.br and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Cdn.siteblindado.com.
Page size can be reduced by 438.9 kB (49%)
887.6 kB
448.7 kB
In fact, the total size of Lindt.com.br main page is 887.6 kB. 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. HTML takes 481.5 kB which makes up the majority of the site volume.
Potential reduce by 431.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 431.3 kB or 90% of the original size.
Potential reduce by 2.9 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, Lindt needs image optimization as it can save up to 2.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 74 B
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 4.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. Lindt.com.br has all CSS files already compressed.
Number of requests can be reduced by 132 (93%)
142
10
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lindt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 116 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
lindt.com.br
100 ms
www.lindt.com.br
2820 ms
calendar.css
56 ms
styles-m.css
66 ms
bootstrap-grid.min.css
101 ms
form-builder.css
102 ms
form-render.css
106 ms
tooltipster.min.css
104 ms
bar-main.css
106 ms
chosen.min.css
112 ms
cookie-consent.css
109 ms
prgdpr.css
111 ms
prgdpr-custom.css
112 ms
rs6.min.css
114 ms
styles-l.css
117 ms
logo-lindt-d_2.png
99 ms
font-awesome.min.css
113 ms
css
118 ms
require.js
112 ms
mixins.js
115 ms
requirejs-config.js
111 ms
js
367 ms
101199.js
402 ms
aw.js
19648 ms
otSDKStub.js
223 ms
js
368 ms
preloader-img.svg
114 ms
gtm.js
182 ms
print.css
147 ms
Optima.woff
220 ms
jquery.js
174 ms
common.js
141 ms
dataPost.js
173 ms
bootstrap.js
141 ms
app.js
174 ms
form-key-provider.js
173 ms
mage-translation-dictionary.js
116 ms
configurable.js
116 ms
theme.js
115 ms
athlete2.woff
128 ms
fontawesome-webfont.woff
421 ms
font
68 ms
domReady.js
45 ms
main.js
45 ms
bootstrap.js
44 ms
jquery-mixin.js
40 ms
jquery-migrate.js
30 ms
template.js
29 ms
confirm.js
30 ms
widget.js
29 ms
text.js
9 ms
underscore.js
63 ms
translate.js
63 ms
price-utils.js
62 ms
price-box.js
61 ms
jquery.parsequery.js
63 ms
fotorama-add-video-events.js
63 ms
types.js
14 ms
layout.js
14 ms
knockout.js
15 ms
knockout-es5.js
14 ms
wrapper.js
14 ms
modal.js
11 ms
engine.js
28 ms
bootstrap.js
24 ms
observable_array.js
26 ms
bound-nodes.js
25 ms
scripts.js
25 ms
version.js
24 ms
mage.js
20 ms
gallery.js
20 ms
main.js
20 ms
registry.js
19 ms
key-codes.js
19 ms
core.js
19 ms
z-index.js
18 ms
js-translation.json
19 ms
vimeo-wrapper.js
17 ms
console-logger.js
15 ms
knockout-repeat.js
12 ms
knockout-fast-foreach.js
14 ms
events.js
13 ms
modal-popup.html
16 ms
renderer.js
15 ms
resizable.js
16 ms
i18n.js
15 ms
scope.js
16 ms
range.js
16 ms
mage-init.js
15 ms
keyboard.js
17 ms
optgroup.js
16 ms
after-render.js
15 ms
autoselect.js
17 ms
datepicker.js
17 ms
outer_click.js
17 ms
fadeVisible.js
20 ms
collapsible.js
18 ms
staticChecked.js
17 ms
simple-checked.js
17 ms
bind-html.js
19 ms
tooltip.js
19 ms
color-picker.js
18 ms
observable_source.js
20 ms
arrays.js
20 ms
compare.js
19 ms
misc.js
21 ms
objects.js
19 ms
strings.js
19 ms
template.js
42 ms
local.js
38 ms
modal-custom.html
38 ms
data.js
26 ms
disable-selection.js
26 ms
focusable.js
26 ms
form.js
28 ms
ie.js
26 ms
keycode.js
26 ms
labels.js
28 ms
jquery-patch.js
27 ms
plugin.js
26 ms
safe-active-element.js
26 ms
safe-blur.js
28 ms
scroll-parent.js
26 ms
tabbable.js
28 ms
unique-id.js
28 ms
logger.js
26 ms
entry-factory.js
26 ms
console-output-handler.js
28 ms
formatter.js
26 ms
message-pool.js
26 ms
levels-pool.js
26 ms
logger-utils.js
27 ms
player.js
26 ms
async.js
26 ms
spectrum.js
21 ms
tinycolor.js
21 ms
class.js
37 ms
modal-slide.html
32 ms
loader.js
21 ms
moment.js
17 ms
load-player.js
12 ms
tooltip.html
13 ms
entry.js
12 ms
dom-observer.js
11 ms
bindings.js
12 ms
owl.carousel.css
133 ms
perfect-scrollbar.min.css
34 ms
127 ms
1011999.js
14 ms
lindt.com.br 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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
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.
lindt.com.br 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
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lindt.com.br 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 Lindt.com.br 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.
lindt.com.br
Open Graph data is detected on the main page of Lindt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: