4.2 sec in total
627 ms
3.3 sec
241 ms
Welcome to wnh.eu homepage info - get ready to check Wnh best content right away, or after learning these important things about wnh.eu
Wah Nam Hong supermarkten heeft alles in huis voor de Aziatische keuken. Bij ons vindt u een breed assortiment aan Chinese kwaliteitsproducten.
Visit wnh.euWe analyzed Wnh.eu page load time and found that the first response time was 627 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wnh.eu performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value31.2 s
0/100
25%
Value18.9 s
0/100
10%
Value8,680 ms
0/100
30%
Value0.012
100/100
15%
Value37.4 s
0/100
10%
627 ms
26 ms
435 ms
177 ms
264 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wnh.eu, 24% (20 requests) were made to Static.xx.fbcdn.net and 20% (17 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Wahnamhong.eu.
Page size can be reduced by 537.8 kB (60%)
891.5 kB
353.7 kB
In fact, the total size of Wnh.eu main page is 891.5 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. 60% of websites need less resources to load. Javascripts take 528.8 kB which makes up the majority of the site volume.
Potential reduce by 20.3 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 20.3 kB or 75% of the original size.
Potential reduce by 3.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. Wnh images are well optimized though.
Potential reduce by 412.7 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 412.7 kB or 78% of the original size.
Potential reduce by 101.7 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. Wnh.eu needs all CSS files to be minified and compressed as it can save up to 101.7 kB or 85% of the original size.
Number of requests can be reduced by 58 (69%)
84
26
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wnh. 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 13 to 1 for CSS and as a result speed up the page load time.
www.wahnamhong.eu
627 ms
css
26 ms
jquery-1.7.1.min.js
435 ms
scripts.js
177 ms
jquery.prettyPhoto.js
264 ms
imagepreloader.js
179 ms
styles.css
465 ms
widgets.css
247 ms
em_quickshop.css
350 ms
jquery.fancybox-1.3.4.css
351 ms
styles.css
419 ms
easyflags.css
478 ms
prototype.js
869 ms
ccard.js
523 ms
validation.js
678 ms
builder.js
604 ms
effects.js
696 ms
dragdrop.js
695 ms
controls.js
780 ms
slider.js
774 ms
js.js
933 ms
form.js
912 ms
menu.js
913 ms
translate.js
944 ms
cookies.js
952 ms
jquery.pikachoose.js
1121 ms
jquery.fancybox-1.3.4.pack.js
1035 ms
em_quickshop.js
1036 ms
small_button_bg_active.png
653 ms
background.png
99 ms
wahnamhong.png
176 ms
top_search_button_bg.gif
178 ms
bkg_button.png
178 ms
cn.gif
186 ms
hk.gif
186 ms
nl.gif
250 ms
us.gif
336 ms
cart_box_corner_left_top.gif
325 ms
cart_box_corner_right_top.gif
323 ms
cart_box_corner_left_bot.gif
340 ms
cart_box_corner_right_bot.gif
340 ms
small_cart_header.png
416 ms
top_menu_divider.gif
642 ms
sub_menu_bg.gif
643 ms
em_quickshop_preview.png
579 ms
top_menu_item_marker.gif
620 ms
likebox.php
340 ms
hDvwL1_H7g-.css
111 ms
56WNbrUYLbL.css
105 ms
yZ--Yu0PDbV.css
113 ms
QD6_ejUFoCN.css
97 ms
xxJgcoj8mOR.css
86 ms
1kPfZUdGrka.js
127 ms
Yuj_Y8xNH2C.js
245 ms
Mpe38fuBVZ2.js
261 ms
n8qIhCw3vMx.js
242 ms
QKy94bWvcbp.js
264 ms
6q5od22S-uf.js
241 ms
7B-2ZS3Qt8r.js
273 ms
qcMicXoOToy.js
280 ms
57RpJa05x58.js
278 ms
65727_317563134966731_149765476_n.jpg
205 ms
print.css
282 ms
398652_293560694033642_1108871523_n.jpg
130 ms
481179_1057304650992572_1366169794826916222_n.jpg
141 ms
1913602_1057304747659229_96030259868094570_n.jpg
139 ms
11937440_1057304820992555_8807225054662458055_n.jpg
230 ms
12791126_1057304897659214_4055353588654129201_n.jpg
138 ms
1934213_1052518844804486_1875262320006411459_n.jpg
134 ms
1915213_1052518851471152_8947448643356513653_n.jpg
156 ms
12802816_1052518864804484_147034681265963713_n.jpg
144 ms
12814164_1052518874804483_2278017189772947823_n.jpg
176 ms
12798869_1052447564811614_1962931076338504102_n.jpg
175 ms
12821502_1052447578144946_1952157502944840392_n.jpg
165 ms
12821429_1048750481847989_1763245139117463473_n.jpg
265 ms
11694909_1044293212293716_7065414756036540091_n.jpg
215 ms
12734189_1044293608960343_4295149655566837375_n.jpg
207 ms
12631524_1044293672293670_4680350450038140833_n.jpg
185 ms
12376306_1044293722293665_4877540153894492689_n.jpg
292 ms
wL6VQj7Ab77.png
111 ms
s7jcwEQH7Sx.png
123 ms
QDwYpIaRyfG.png
122 ms
K00K-UgnsKu.png
111 ms
VXcANLwwL5J.js
3 ms
AmlxWlqMvlv.js
24 ms
wnh.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
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
[id] attributes on active, focusable elements are not unique
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
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.
wnh.eu 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
General
Impact
Issue
Detected JavaScript libraries
wnh.eu 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
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 Wnh.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 Wnh.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.
wnh.eu
Open Graph description is not detected on the main page of Wnh. 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: