3.4 sec in total
172 ms
3 sec
273 ms
Click here to check amazing Itworks content for Belgium. Otherwise, check out these important facts you probably never knew about itworks.be
Knowledge and Skills to Turn Problems into Solutions:
Visit itworks.beWe analyzed Itworks.be page load time and found that the first response time was 172 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
itworks.be performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value8.8 s
1/100
25%
Value7.6 s
26/100
10%
Value5,690 ms
0/100
30%
Value0.002
100/100
15%
Value17.0 s
4/100
10%
172 ms
323 ms
83 ms
107 ms
90 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Itworks.be, 13% (18 requests) were made to Dsms0mj1bbhn4.cloudfront.net and 8% (11 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (833 ms) relates to the external source Va.tawk.to.
Page size can be reduced by 1.9 MB (68%)
2.8 MB
894.5 kB
In fact, the total size of Itworks.be main page is 2.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 273.0 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 273.0 kB or 89% of the original size.
Potential reduce by 15.1 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, Itworks needs image optimization as it can save up to 15.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 MB
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 1.4 MB or 67% of the original size.
Potential reduce by 182.4 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. Itworks.be needs all CSS files to be minified and compressed as it can save up to 182.4 kB or 81% of the original size.
Number of requests can be reduced by 92 (77%)
119
27
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itworks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
itworks.be
172 ms
www.itworks.be
323 ms
css
83 ms
css
107 ms
bootstrap.min.css
90 ms
bootstrap-theme.min.css
104 ms
font-awesome.min.css
100 ms
jquery.min.js
103 ms
bootstrap.min.js
102 ms
itworks.css
97 ms
slim-081711.css
95 ms
ITWorks_logo_25Years.png
148 ms
shareaholic.js
110 ms
in.js
123 ms
conversion.js
133 ms
cse.js
339 ms
fbevents.js
91 ms
b04f72ad5a125dca06726ffe422ef4a9.json
182 ms
raven.min.js
80 ms
secureAnonymousFramework
30 ms
snapabug.js
166 ms
1662100254040263
88 ms
shrMain.min.js
94 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
109 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
131 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
149 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
150 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
184 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
149 ms
fontawesome-webfont.woff
41 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
148 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
179 ms
74 ms
blank.gif
164 ms
analytics.js
123 ms
bat.js
144 ms
85 ms
jquery.min.js
32 ms
lodash.min.js
82 ms
URI.js
140 ms
most.min.js
143 ms
punycode.min.js
137 ms
default
296 ms
script.js
243 ms
insight.min.js
133 ms
xdrpc.html
45 ms
angular.min.js
40 ms
followcompany
181 ms
jsapi
178 ms
178 ms
IPv6.min.js
4 ms
SecondLevelDomains.min.js
19 ms
pageview.gif
363 ms
css
296 ms
anonymoususerspace
93 ms
js
345 ms
css
392 ms
js
398 ms
app.js
90 ms
app.js
255 ms
default+en.css
45 ms
default.css
87 ms
default+en.I.js
159 ms
vglnk.js
292 ms
partners.js
380 ms
shareaholic_logo_mark.svg
211 ms
logo.svg
232 ms
analytics.svg
290 ms
apps.svg
220 ms
contentlibrary.svg
218 ms
earnings.svg
252 ms
settings.svg
251 ms
help.svg
290 ms
close.svg
276 ms
shareaholic-logo.svg
292 ms
close-white.svg
297 ms
smile_message_en.png
215 ms
ga-audiences
181 ms
icons.png
282 ms
emojione.min.css
294 ms
emojione.min.js
309 ms
1504666248261
833 ms
ajax-loader.gif
304 ms
share-knowledge.png
195 ms
share-button-shadow.png
165 ms
shareaholic-icons.woff
166 ms
async-ads.js
118 ms
googlelogo_lightgrey_46x16dp.png
46 ms
googlelogo_grey_46x15dp.png
46 ms
search_box_icon.png
50 ms
clear.png
110 ms
nav_logo114.png
91 ms
share
44 ms
graph.facebook.com
206 ms
user_info
181 ms
pixel.gif
53 ms
pixel.gif
85 ms
sholic.js
624 ms
dpx.js
76 ms
YNMJrK4lsMAJlxSsJDb17LW8YmmHRLakZxkWagp6
82 ms
beacon.js
583 ms
afsh.js
75 ms
sprite_connect_v15.png
54 ms
rpc
504 ms
p
547 ms
dpx
428 ms
tpid=be6e5631-82a7-405f-8a2f-5edd9f4d2979
427 ms
kitten
469 ms
134 ms
v2
126 ms
ping
151 ms
ajax-loader-3.gif
45 ms
171 ms
events
44 ms
39 ms
eps
285 ms
362248.gif
6 ms
genp=IAB+Category_Business
56 ms
dduid_sync
112 ms
domains
49 ms
362248.gif
5 ms
s-3261.xgi
20 ms
119 ms
40932
150 ms
145 ms
v3
58 ms
rtset
51 ms
Pug
67 ms
379208.gif
10 ms
pixel
72 ms
ecc
28 ms
sd
6 ms
cm
98 ms
epx.gif
81 ms
sync
20 ms
ermcm
49 ms
tap.php
6 ms
16 ms
itworks.be 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
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
itworks.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
itworks.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itworks.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Itworks.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.
itworks.be
Open Graph data is detected on the main page of Itworks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: