4.6 sec in total
688 ms
3.7 sec
259 ms
Welcome to grandhall.eu homepage info - get ready to check Grandhall best content right away, or after learning these important things about grandhall.eu
Visit grandhall.euWe analyzed Grandhall.eu page load time and found that the first response time was 688 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Grandhall.eu rating and web reputation
grandhall.eu performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value8.4 s
2/100
25%
Value10.0 s
9/100
10%
Value790 ms
37/100
30%
Value0.774
5/100
15%
Value7.8 s
44/100
10%
688 ms
63 ms
313 ms
404 ms
328 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 84% of them (64 requests) were addressed to the original Grandhall.eu, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Grandhall.eu.
Page size can be reduced by 324.1 kB (26%)
1.2 MB
904.3 kB
In fact, the total size of Grandhall.eu main page is 1.2 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. 45% of websites need less resources to load. Images take 931.9 kB which makes up the majority of the site volume.
Potential reduce by 25.2 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 8.3 kB, which is 25% 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 25.2 kB or 77% of the original size.
Potential reduce by 102.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. Obviously, Grandhall needs image optimization as it can save up to 102.0 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 196.9 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 196.9 kB or 75% of the original size.
Number of requests can be reduced by 21 (41%)
51
30
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grandhall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
grandhall.eu
688 ms
jquery.min.js
63 ms
CssLoader.aspx
313 ms
JsLoader.aspx
404 ms
showOnce.js
328 ms
JsLoader.aspx
261 ms
css
35 ms
css
48 ms
WebResource.axd
301 ms
ScriptResource.axd
485 ms
ScriptResource.axd
464 ms
jquery-ui.js
15 ms
jquery.cycle.all.js
559 ms
Functions.js
371 ms
analytics.js
26 ms
no_image_recepten_small.jpg
677 ms
bg.jpg
191 ms
switch_left.png
190 ms
logo.png
192 ms
bbq_weer.png
192 ms
actie_button.png
223 ms
bbq_button.png
263 ms
a2c83116df9a99c6606b003435132b7e-160x153.jpeg
505 ms
edbdf03c042a70cbbd5fc7af887eb60b-198x198.png
477 ms
8224b60b9978645027947b05b3c6036d-198x198.png
432 ms
e30e519becd70f9bb7073de1ea5e9d04-198x198.png
461 ms
066f12d7bfa164eb03ec162a968dcfe9-198x198.png
574 ms
60eb24f022ba9f79b2b17d690b034819-198x198.png
614 ms
Woodchips_thumb.jpg
687 ms
bbq_thumb.jpg
665 ms
buitenhaard_thumb.jpg
738 ms
4b2115f0a4dd9bde4699e7deaee1c7ee-198x198.png
826 ms
recept.jpg
702 ms
brochureEN.png
751 ms
jquery.cookie.js
49 ms
fbutton.png
831 ms
collect
17 ms
select-language.html
965 ms
topbar.jpg
753 ms
search_field.png
774 ms
search_icon.png
781 ms
home_icon.png
841 ms
slider_block_grass.png
851 ms
link_pijl.png
869 ms
featured_bg.png
895 ms
footer_block_bg.png
892 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
8 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
17 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
18 ms
slider_nav_button_active.png
124 ms
slider_nav_button.png
116 ms
jquery.min.js
23 ms
grandhall_logo.png
437 ms
slogan.png
422 ms
headerAfb.png
1596 ms
headerAfb1.jpg
678 ms
headerAfb2.jpg
1040 ms
bbq_sign.png
549 ms
barbecue.png
987 ms
contentBG.png
649 ms
Netherlands.png
666 ms
Belgium.png
765 ms
Germany.png
801 ms
Austria.png
806 ms
Switzerland.png
899 ms
United_Kingdom.png
931 ms
Italy.png
930 ms
France.png
1013 ms
Denmark.png
1042 ms
Sweden.png
1048 ms
European_Union.png
1113 ms
footerBG.png
1307 ms
odeon.png
306 ms
egrill.png
142 ms
chicken_roaster.png
330 ms
heatstrip.png
213 ms
grandhall.eu 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
Links do not have a discernible name
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.
grandhall.eu 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
Page has valid source maps
grandhall.eu SEO score
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grandhall.eu can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Grandhall.eu 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.
grandhall.eu
Open Graph description is not detected on the main page of Grandhall. 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: