3.5 sec in total
622 ms
2.5 sec
354 ms
Visit infozine.be now to see the best up-to-date Infozine content for Belgium and also check out these interesting facts you probably never knew about infozine.be
Visit infozine.beWe analyzed Infozine.be page load time and found that the first response time was 622 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster. This domain responded with an error, which can significantly jeopardize Infozine.be rating and web reputation
infozine.be performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value4.2 s
44/100
25%
Value5.6 s
53/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value6.4 s
59/100
10%
622 ms
537 ms
88 ms
165 ms
291 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 50% of them (27 requests) were addressed to the original Infozine.be, 17% (9 requests) were made to Cdn.videogamesvalley.com and 9% (5 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (622 ms) belongs to the original domain Infozine.be.
Page size can be reduced by 1.0 MB (63%)
1.6 MB
577.3 kB
In fact, the total size of Infozine.be main page is 1.6 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 161.1 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 161.1 kB or 76% of the original size.
Potential reduce by 841 B
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. Infozine images are well optimized though.
Potential reduce by 752.5 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 752.5 kB or 65% of the original size.
Potential reduce by 88.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. Infozine.be needs all CSS files to be minified and compressed as it can save up to 88.0 kB or 87% of the original size.
Number of requests can be reduced by 40 (83%)
48
8
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Infozine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
infozine.be
622 ms
www.infozine.be
537 ms
style.css
88 ms
swfobject.js
165 ms
%20jquery-ui.min.css
291 ms
lib-mjd.min.css
296 ms
pagenavi-css.css
168 ms
pro.css
298 ms
thecolors.css
303 ms
jquery.min.js
30 ms
%20jquery-ui.min.js
320 ms
lib-mjd.min.js
321 ms
addthis_widget.js
11 ms
addthis_widget.js
16 ms
wp-embed.min.js
167 ms
reset.css
86 ms
wp_core.css
160 ms
theme.css
166 ms
custom.css
165 ms
ti.js
16 ms
wp-emoji-release.min.js
122 ms
analytics.js
32 ms
bgblue.jpg
96 ms
social_icon_sprite.png
95 ms
header-mobile-banner4-default-w100px-01.png
508 ms
hl-dot-black.gif
92 ms
bg_nav.png
93 ms
nav-black.png
294 ms
bgcontent.gif
342 ms
post-bg.gif
341 ms
post-footer-bg.gif
341 ms
comment_count_bg.png
340 ms
bg_sidebar.png
340 ms
box-bgr.gif
394 ms
festival-checklist-app-web-promo-v1-400px-01.png
553 ms
boekentas-webapp-promo-v1-250px-var4-01.jpg
465 ms
search-btn.png
390 ms
lightgrayup.png
387 ms
box-bgr.gif
89 ms
fbox-dividers.png
92 ms
p
230 ms
bpX4VUZo0r34nyadbi-bnq.js
277 ms
collect
271 ms
layers.e5ea973510bf60b3db41.js
191 ms
300lo.json
74 ms
overlay.png
84 ms
sh.8e5f85691f9aaa082472a194.html
63 ms
nl.js
27 ms
v2
43 ms
dpx
7 ms
ca.png
156 ms
pixel
28 ms
xrefid.xgi
7 ms
pixel
17 ms
infozine.be accessibility score
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
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.
infozine.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
infozine.be 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
N/A
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infozine.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Dutch. Our system also found out that Infozine.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.
infozine.be
Open Graph description is not detected on the main page of Infozine. 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: