3.3 sec in total
598 ms
2.5 sec
246 ms
Click here to check amazing Griekse Huis content for Netherlands. Otherwise, check out these important facts you probably never knew about grieksehuis.nl
De lekkerste Griekse producten koopt u bij het Griekse Huis. Van Griekse wijnen tot delicatessen en sterke dranken.
Visit grieksehuis.nlWe analyzed Grieksehuis.nl page load time and found that the first response time was 598 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
grieksehuis.nl performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value9.2 s
1/100
25%
Value7.3 s
28/100
10%
Value190 ms
91/100
30%
Value0.065
97/100
15%
Value12.7 s
14/100
10%
598 ms
78 ms
36 ms
78 ms
74 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 94% of them (136 requests) were addressed to the original Grieksehuis.nl, 3% (4 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (598 ms) belongs to the original domain Grieksehuis.nl.
Page size can be reduced by 106.1 kB (18%)
573.8 kB
467.7 kB
In fact, the total size of Grieksehuis.nl main page is 573.8 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. 70% of websites need less resources to load. Images take 361.8 kB which makes up the majority of the site volume.
Potential reduce by 93.4 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 15.6 kB, which is 14% 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 93.4 kB or 86% of the original size.
Potential reduce by 10.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. Griekse Huis images are well optimized though.
Potential reduce by 17 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 2.0 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. Grieksehuis.nl has all CSS files already compressed.
Number of requests can be reduced by 116 (84%)
138
22
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Griekse Huis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 106 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
www.grieksehuis.nl
598 ms
calendar.css
78 ms
styles-m.css
36 ms
swiper.min.css
78 ms
magnific-popup.css
74 ms
styles-l.css
78 ms
css
81 ms
font-awesome.css
69 ms
style.css
85 ms
custom.css
81 ms
require.js
83 ms
mixins.js
301 ms
requirejs-config.js
86 ms
general.js
87 ms
email-decode.min.js
85 ms
css
16 ms
css
23 ms
banner-homepage.jpg
20 ms
English.png
19 ms
logo.png
21 ms
chrisanthidis_kourabie_1.png
55 ms
1287.jpg
21 ms
5c.png
55 ms
p1000311_-_kopie.jpg
57 ms
makvelmakkaronipastitsio_1.jpg
55 ms
mythosbier.jpg
57 ms
iliadablack.jpg
55 ms
kostas-griekse-huis.jpg
56 ms
NIX18_diap.png
58 ms
kostas-griekse-huis-II.jpg
59 ms
logo-footer.png
247 ms
betaalmogelijkheden.png
246 ms
jquery.js
56 ms
common.js
56 ms
dataPost.js
75 ms
bootstrap.js
76 ms
app.js
71 ms
form-key-provider.js
253 ms
mage-translation-dictionary.js
71 ms
theme.js
266 ms
am-recaptcha.js
33 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
46 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
46 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
49 ms
fontawesome-webfont.woff
25 ms
Luma-Icons.woff
43 ms
jquery-migrate.js
30 ms
domReady.js
28 ms
jquery-mixin.js
34 ms
template.js
25 ms
confirm.js
45 ms
widget.js
61 ms
main.js
253 ms
bootstrap.js
66 ms
knockout.js
480 ms
underscore.js
165 ms
text.js
363 ms
types.js
161 ms
layout.js
163 ms
WWXRlj2DZQiMJYaYRoJXKdU.ttf
10 ms
wrapper.js
281 ms
translate.js
340 ms
modal.js
142 ms
knockout-es5.js
140 ms
version.js
151 ms
engine.js
163 ms
bootstrap.js
396 ms
observable_array.js
187 ms
bound-nodes.js
212 ms
main.js
135 ms
smart-keyboard-handler.js
146 ms
mage.js
160 ms
ie-class-fixer.js
159 ms
registry.js
171 ms
console-logger.js
170 ms
key-codes.js
166 ms
core.js
172 ms
z-index.js
192 ms
observable_source.js
149 ms
renderer.js
144 ms
scripts.js
149 ms
events.js
105 ms
arrays.js
85 ms
compare.js
343 ms
misc.js
89 ms
objects.js
97 ms
strings.js
95 ms
template.js
103 ms
local.js
77 ms
logger.js
71 ms
entry-factory.js
87 ms
console-output-handler.js
84 ms
formatter.js
90 ms
message-pool.js
96 ms
levels-pool.js
100 ms
logger-utils.js
98 ms
js-translation.json
303 ms
modal-popup.html
209 ms
modal-slide.html
309 ms
modal-custom.html
329 ms
data.js
113 ms
disable-selection.js
124 ms
focusable.js
137 ms
form.js
149 ms
ie.js
162 ms
keycode.js
175 ms
labels.js
386 ms
jquery-patch.js
208 ms
plugin.js
219 ms
safe-active-element.js
230 ms
safe-blur.js
241 ms
scroll-parent.js
254 ms
tabbable.js
263 ms
unique-id.js
276 ms
class.js
275 ms
loader.js
380 ms
moment.js
231 ms
entry.js
234 ms
knockout-repeat.js
413 ms
knockout-fast-foreach.js
219 ms
resizable.js
209 ms
i18n.js
223 ms
scope.js
220 ms
range.js
418 ms
mage-init.js
432 ms
keyboard.js
436 ms
optgroup.js
288 ms
after-render.js
499 ms
autoselect.js
309 ms
datepicker.js
325 ms
outer_click.js
340 ms
fadeVisible.js
361 ms
collapsible.js
369 ms
staticChecked.js
369 ms
simple-checked.js
373 ms
bind-html.js
362 ms
tooltip.js
561 ms
color-picker.js
344 ms
async.js
222 ms
spectrum.js
18 ms
tinycolor.js
13 ms
dom-observer.js
16 ms
bindings.js
16 ms
tooltip.html
115 ms
print.css
30 ms
grieksehuis.nl 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
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
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
grieksehuis.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
grieksehuis.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grieksehuis.nl 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 Grieksehuis.nl 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.
grieksehuis.nl
Open Graph description is not detected on the main page of Griekse Huis. 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: