10.3 sec in total
510 ms
9.4 sec
377 ms
Welcome to de.husse.com homepage info - get ready to check De Husse best content for Netherlands right away, or after learning these important things about de.husse.com
Visit de.husse.comWe analyzed De.husse.com page load time and found that the first response time was 510 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
de.husse.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value11.0 s
0/100
25%
Value11.8 s
4/100
10%
Value990 ms
28/100
30%
Value0.766
5/100
15%
Value12.1 s
16/100
10%
510 ms
606 ms
694 ms
615 ms
892 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 94% of them (72 requests) were addressed to the original De.husse.com, 3% (2 requests) were made to Stats.g.doubleclick.net and 3% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.4 sec) relates to the external source Stats.g.doubleclick.net.
Page size can be reduced by 785.6 kB (19%)
4.0 MB
3.3 MB
In fact, the total size of De.husse.com main page is 4.0 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. 80% 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 3.3 MB which makes up the majority of the site volume.
Potential reduce by 80.8 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 80.8 kB or 86% of the original size.
Potential reduce by 167.4 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. De Husse images are well optimized though.
Potential reduce by 274.1 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 274.1 kB or 70% of the original size.
Potential reduce by 263.3 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. De.husse.com needs all CSS files to be minified and compressed as it can save up to 263.3 kB or 91% of the original size.
Number of requests can be reduced by 29 (39%)
74
45
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of De Husse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
de.husse.com
510 ms
www.de.husse.com
606 ms
694 ms
cf0_site.css
615 ms
cf0_site_de_nrm_262.css
892 ms
dojo.js
1045 ms
MiniSlideShow.js
258 ms
pricecalc.js
263 ms
awstats_misc_tracker.js
272 ms
dc.js
4430 ms
2558628921.gif
4390 ms
3762893660.png
4391 ms
.tel_30x30.thumb-30x30.png
4391 ms
.email_110x110.thumb-110x110.png
4393 ms
upload_husse_webshop_logo2.gif
4397 ms
1086623274.png
4394 ms
.husseW_dog.thumb.gif
4397 ms
.husseW_cat.thumb.gif
4398 ms
.husseW_horse.thumb.gif
4399 ms
upload_HusseGermany_Header.jpg
4402 ms
2265721859.png
4400 ms
Lamm&Ris_746x300pt.jpg
4403 ms
.Optimal_746x300pt.thumb-746x300.jpg
4405 ms
.Exclusive_Outdoor_746x300pt.thumb-746x300.jpg
4408 ms
.Tuna-Kyckling_i_Gel%C3%A9_746x300pt.thumb-746x300.jpg
4405 ms
Kex&Rollies.jpg
4409 ms
.Kristall_Minus_746x300pt.thumb-746x300.jpg
4411 ms
.Parasit_Minus_746x300pt.thumb-746x300.jpg
4413 ms
Tick&Flea_Minus_746x300pt.jpg
4417 ms
.Bug_Minus.thumb-746x300.jpg
4418 ms
.H%C3%A4st_Shampoo.thumb-746x300.jpg
4422 ms
arrow_left2_888888.gif
4409 ms
arrow_right2_888888.gif
4412 ms
jump_round1_black.gif
4413 ms
jump_round1_888888.gif
4415 ms
1706163445T.png
4417 ms
1706163445M.png
4415 ms
bgH1special.gif
4418 ms
.Easter_Dog_DE.thumb-300x300.jpg
4419 ms
.Easter_Cat_DE.thumb-300x300.jpg
4420 ms
1706163445B.png
4418 ms
.Prima_Plus_247x300pt.thumb-247x300.jpg
4421 ms
.Insect_Minus_50ml_247x300pt.thumb-247x300.jpg
4421 ms
.Digestion_Plus_247x300pt.thumb-247x300.jpg
4422 ms
.Exclusive_Katt_Sterilised_247x300pt.thumb-247x300.jpg
4422 ms
.Eco_Kattstroe_247x300pt.thumb-247x300.jpg
606 ms
like.php
135 ms
.Futternaepfe_247x300pt.thumb-247x300.jpg
659 ms
product-icons_Chicken-Based-b.jpg
277 ms
product-icons_Balanced-Nutrition-b.jpg
276 ms
product-icons_Mobility-b.jpg
277 ms
product-icons_Energy_-b.jpg
282 ms
product-icons_EnergyControlbig.jpg
530 ms
product-icons_Coat-b.jpg
527 ms
product-icons_EyeHealth_-b.jpg
535 ms
product-icons_GlutenFree-b.jpg
532 ms
1884093049.png
782 ms
eShoppingCart_icon.gif
772 ms
.husse_world_map_widget_new_may_thumb_179x75.thumb-180x75.jpg
784 ms
bull1.gif
780 ms
.Facebook.thumb-180x150.jpg
1064 ms
.Zertifikate.thumb-180x50.jpg
1013 ms
776894965T.png
1027 ms
776894965M.png
1026 ms
.image004.thumb-50x50.png
1027 ms
.image003.thumb-50x50.png
1039 ms
.image001.thumb-50x49.png
1263 ms
776894965B.png
1265 ms
1784619698.png
1275 ms
1164990008.png
1275 ms
1106689618.png
1285 ms
4024268148.png
1314 ms
131092214.png
1501 ms
awstats_misc_tracker.js
1511 ms
__utm.gif
16 ms
TY3MhkXpWJ-.js
285 ms
LVx-xkvaJ0b.png
323 ms
de.husse.com 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
[aria-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
de.husse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
de.husse.com 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
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise De.husse.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that De.husse.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.
de.husse.com
Open Graph description is not detected on the main page of De Husse. 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: