2.5 sec in total
51 ms
2 sec
416 ms
Welcome to lindt.bg homepage info - get ready to check Lindt best content for Bulgaria right away, or after learning these important things about lindt.bg
Открийте света на шоколада Lindt & Sprungli; разгледайте пълната ни гама шоколdди, изкушения и бонбониери, авторски рецепти и нови продукти от шоколадовия свят на Lindt.
Visit lindt.bgWe analyzed Lindt.bg page load time and found that the first response time was 51 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lindt.bg performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value9.7 s
0/100
25%
Value13.4 s
2/100
10%
Value3,810 ms
1/100
30%
Value0
100/100
15%
Value23.2 s
1/100
10%
51 ms
158 ms
99 ms
93 ms
249 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 99% of them (74 requests) were addressed to the original Lindt.bg, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (699 ms) belongs to the original domain Lindt.bg.
Page size can be reduced by 290.3 kB (12%)
2.4 MB
2.1 MB
In fact, the total size of Lindt.bg main page is 2.4 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 237.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. 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 237.9 kB or 88% of the original size.
Potential reduce by 986 B
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. Lindt images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 49.4 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.bg needs all CSS files to be minified and compressed as it can save up to 49.4 kB or 16% of the original size.
Number of requests can be reduced by 25 (42%)
60
35
The browser has sent 60 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 15 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.lindt.bg
51 ms
styles-m.min.css
158 ms
adyen.min.css
99 ms
tooltipster.min.css
93 ms
lightbox.min.css
249 ms
bootstrap-tiny.min.css
95 ms
owl.carousel.min.css
94 ms
font-awesome.min.css
228 ms
animate.min.css
230 ms
bootstrap-tiny.min.css
231 ms
carousel.min.css
231 ms
styles-l.min.css
238 ms
require.min.js
256 ms
disabled.min.js
254 ms
requirejs-min-resolver.min.js
254 ms
mixins.min.js
257 ms
requirejs-config.min.js
319 ms
responsiveslides.min.js
336 ms
cart-mini.min.js
336 ms
gtm.js
111 ms
logo.png
129 ms
logo-small.png
129 ms
logo-small--white.png
114 ms
lindor-cornet-mlechen-200.png
83 ms
lindor-cornet-assorti-200.png
268 ms
lindt-excellence-70.png
103 ms
lindor-cornet-leshnik-200.png
266 ms
lindt-excellence-78.png
168 ms
lindor-cornet-noir-200g.png
246 ms
lindt-excellence-85.png
311 ms
lindor_mlechen_stick.png
311 ms
lindt-excellence-90.png
245 ms
lindt_swiss_classic_leshnik_stafidi.png
266 ms
lindt-excellence-orange.png
352 ms
lindt_gold_mlechen_1.png
266 ms
swiss-classic-mlechen-100.png
267 ms
lindt_gold_mlechen_leshnik.png
267 ms
swiss_classic_dvoino_mlechen.png
374 ms
lindt_gold_mlechen_badem.png
433 ms
lindt-excellence-limon.png
581 ms
swiss-classic-mlechen-badem-100.png
380 ms
lindt_excellence_karamel_morska_sol_1.png
311 ms
swiss-classic-mlechen-leshnik-100.png
312 ms
lindor_mlechen_shokolad.png
517 ms
lindor_cornet_byal_200.png
432 ms
lindor-cornet-mlechen-500.png
579 ms
lindt-excellence-99.png
383 ms
facebook.png
462 ms
instagram.png
510 ms
magentoStorefrontEvents.min.js
578 ms
roboto-v20-latin_cyrillic-regular.woff
545 ms
roboto-v20-latin_cyrillic-300.woff
592 ms
roboto-v20-latin_cyrillic-700.woff
601 ms
jquery.min.js
622 ms
a9458453-c860-4807-8865-5c9b26f9fa5c.woff
699 ms
2c711925-2b63-49ab-b5a8-7bba5187bab7.woff
602 ms
lindt-icons.ttf
581 ms
hover-intent.min.js
646 ms
scrollInDiv.min.js
688 ms
Master-chocolatier-pouring-chocolate-1440x800.jpg
600 ms
Lindt_coconut_banner-1440x800_2_2.png
606 ms
Praline1440x800_2.jpg
586 ms
HomeofChoc_gradient1320x550.jpg
581 ms
amScrollScript.min.js
612 ms
bootstrap.min.js
520 ms
weltpixel_persistentLayer.min.js
586 ms
weltpixel_gtm.min.js
597 ms
customer-data.min.js
578 ms
underscore.min.js
84 ms
ko.min.js
180 ms
section-config.min.js
80 ms
url.min.js
81 ms
storage.min.js
88 ms
jquery-storageapi.min.js
398 ms
print.min.css
81 ms
lindt.bg 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
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.
lindt.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
lindt.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 doesn't use legible font sizes
Tap targets are not sized appropriately
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lindt.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Lindt.bg 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.bg
Open Graph description is not detected on the main page of Lindt. 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: