6.6 sec in total
368 ms
5.9 sec
336 ms
Click here to check amazing Zahia content. Otherwise, check out these important facts you probably never knew about zahia.be
Zahia biedt u een uitzonderlijke collectie halfedelstenen, oude glaskralen en organiseert ook workshops juwelen maken
Visit zahia.beWe analyzed Zahia.be page load time and found that the first response time was 368 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zahia.be performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value8.4 s
2/100
25%
Value6.9 s
33/100
10%
Value270 ms
82/100
30%
Value0.251
49/100
15%
Value8.9 s
34/100
10%
368 ms
2058 ms
64 ms
905 ms
587 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 73% of them (44 requests) were addressed to the original Zahia.be, 7% (4 requests) were made to Zahia.disqus.com and 5% (3 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Zahia.be.
Page size can be reduced by 307.1 kB (26%)
1.2 MB
869.6 kB
In fact, the total size of Zahia.be 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. 40% of websites need less resources to load. Images take 891.5 kB which makes up the majority of the site volume.
Potential reduce by 72.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 72.8 kB or 79% of the original size.
Potential reduce by 120.2 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, Zahia needs image optimization as it can save up to 120.2 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 33.6 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 33.6 kB or 33% of the original size.
Potential reduce by 80.5 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. Zahia.be needs all CSS files to be minified and compressed as it can save up to 80.5 kB or 88% of the original size.
Number of requests can be reduced by 26 (53%)
49
23
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zahia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
zahia.be
368 ms
www.zahia.be
2058 ms
gtm.js
64 ms
all.css
905 ms
modernizr.custom.js
587 ms
jquery-1.7.2.min.js
935 ms
validation.js
420 ms
jquery.touchswipe.1.1.1.js
419 ms
init.js
419 ms
jquery.flexslider.js
668 ms
jquery.easing.js
668 ms
jquery.placeholder.js
805 ms
jquery.ui.totop.js
1006 ms
jquery.selectbox-0.2.js
928 ms
hotjar-636607.js
93 ms
pinit.js
14 ms
pattern-body.png
478 ms
ga.js
31 ms
pin_it_button.png
25 ms
pattern-green.png
388 ms
pattern-header.png
388 ms
header-bottom.gif
195 ms
divider-dots.png
387 ms
sprite-ui.png
837 ms
webshop-badge.png
846 ms
pattern-orange.png
584 ms
thumbnail.aspx
1395 ms
visual-bottom.gif
585 ms
arrow-orange-small.png
585 ms
242542528_4095244610599058_9125263865345556014_n.jpg
1059 ms
0.jpg
1312 ms
0.jpg
990 ms
voorzorgsmaatregelen.jpg
1313 ms
thumbnail.aspx
1653 ms
thumbnail.aspx
1614 ms
thumbnail.aspx
1635 ms
banner-webshop.png
2513 ms
pattern-light-brown.png
1616 ms
desktop-workshops.png
1615 ms
circled.png
1689 ms
instagram.png
1718 ms
footer-top.gif
1706 ms
Asap-Regular-webfont.woff
1724 ms
Asap-Bold-webfont.woff
1737 ms
__utm.gif
41 ms
arrow-lightorange-small.png
1731 ms
pattern-input-footer.png
1768 ms
Asap-Italic-webfont.woff
1774 ms
count.js
36 ms
getcart
133 ms
count.js
72 ms
collect
83 ms
arrow-down.png
1741 ms
pinit_main.js
158 ms
fbevents.js
32 ms
44 ms
count-data.js
4 ms
count-data.js
49 ms
showcart
158 ms
bg_direction_nav.png
158 ms
zahia.be 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
zahia.be 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
zahia.be 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 Zahia.be 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 Zahia.be 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.
zahia.be
Open Graph description is not detected on the main page of Zahia. 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: