2.7 sec in total
164 ms
2.2 sec
276 ms
Visit horreia.com now to see the best up-to-date Horreia content and also check out these interesting facts you probably never knew about horreia.com
Horreia Company - Horreia is Market-Leader in Domestic Market Position in hard candy industry
Visit horreia.comWe analyzed Horreia.com page load time and found that the first response time was 164 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.
horreia.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value9.7 s
0/100
25%
Value6.6 s
37/100
10%
Value80 ms
99/100
30%
Value0.002
100/100
15%
Value8.3 s
39/100
10%
164 ms
383 ms
80 ms
161 ms
231 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 78% of them (70 requests) were addressed to the original Horreia.com, 16% (14 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Horreia.com.
Page size can be reduced by 567.2 kB (12%)
4.6 MB
4.0 MB
In fact, the total size of Horreia.com main page is 4.6 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 3.9 MB which makes up the majority of the site volume.
Potential reduce by 32.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 10.3 kB, which is 27% 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 32.0 kB or 84% of the original size.
Potential reduce by 497.6 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, Horreia needs image optimization as it can save up to 497.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 22.2 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 15.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. Horreia.com has all CSS files already compressed.
Number of requests can be reduced by 49 (70%)
70
21
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horreia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
horreia.com
164 ms
horreia.com
383 ms
animate.css
80 ms
bootstrap.min.css
161 ms
et-line-icons.css
231 ms
font-awesome.min.css
237 ms
themify-icons.css
235 ms
swiper.min.css
236 ms
justified-gallery.min.css
234 ms
magnific-popup.css
239 ms
settings.css
308 ms
layers.css
319 ms
navigation.css
314 ms
bootsnav.css
317 ms
style.css
401 ms
responsive.css
335 ms
swiper-bundle.min.css
29 ms
css2
33 ms
css2
49 ms
app_site.css
464 ms
vue.js
556 ms
jquery.js
496 ms
modernizr.js
396 ms
bootstrap.min.js
414 ms
jquery.easing.1.3.js
475 ms
skrollr.min.js
480 ms
smooth-scroll.js
492 ms
jquery.appear.js
541 ms
bootsnav.js
554 ms
jquery.nav.js
620 ms
wow.min.js
620 ms
swiper.min.js
620 ms
jquery.count-to.js
621 ms
jquery.stellar.js
638 ms
jquery.magnific-popup.min.js
638 ms
isotope.pkgd.min.js
682 ms
imagesloaded.pkgd.min.js
701 ms
classie.js
701 ms
hamburger-menu.js
720 ms
counter.js
727 ms
jquery.fitvids.js
726 ms
swiper-bundle.min.css
12 ms
equalize.min.js
655 ms
skill.bars.jquery.js
606 ms
justified-gallery.min.js
540 ms
jquery.easypiechart.min.js
571 ms
instafeed.min.js
573 ms
retina.min.js
569 ms
jquery.themepunch.tools.min.js
571 ms
jquery.themepunch.revolution.min.js
608 ms
swiper-bundle.js
540 ms
app.js
732 ms
css
16 ms
css
26 ms
padlock.svg
396 ms
logo-white.png
337 ms
cancel.png
306 ms
HomeSlider_81306.jpg
575 ms
chevron-left.svg
348 ms
chevron-right.svg
384 ms
home_horreiaDo_img.gif
959 ms
home--section.png
810 ms
Icon_Saula57369.svg
462 ms
Saula80465.gif
779 ms
Icon_Elite95769.svg
703 ms
Elite38558.gif
696 ms
Icon_Chicohend38041.svg
655 ms
Chicohend43453.gif
776 ms
home_values_img.gif
811 ms
home-form.png
1046 ms
footer-facebook.svg
814 ms
S6uyw4BMUTPHvxk.ttf
72 ms
S6u9w4BMUTPHh7USew8.ttf
89 ms
S6u8w4BMUTPHh30wWw.ttf
98 ms
S6u9w4BMUTPHh6UVew8.ttf
99 ms
S6u9w4BMUTPHh50Xew8.ttf
98 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
100 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
99 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
97 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
117 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
115 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
116 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
117 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
116 ms
fa-solid-900.woff
834 ms
fa-regular-400.woff
829 ms
footer-youtube.svg
827 ms
send-mail.png
812 ms
logo.svg
842 ms
horreia.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
horreia.com 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
horreia.com 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
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
![]()
EN
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Horreia.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Horreia.com 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.
horreia.com
Open Graph data is detected on the main page of Horreia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: