4.9 sec in total
292 ms
3.5 sec
1.1 sec
Click here to check amazing Dynatek content for Belgium. Otherwise, check out these important facts you probably never knew about dynatek.be
Visit dynatek.beWe analyzed Dynatek.be page load time and found that the first response time was 292 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
dynatek.be performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value18.8 s
0/100
25%
Value6.8 s
35/100
10%
Value170 ms
93/100
30%
Value0.745
6/100
15%
Value14.7 s
8/100
10%
292 ms
734 ms
68 ms
87 ms
159 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 72% of them (63 requests) were addressed to the original Dynatek.be, 6% (5 requests) were made to F.vimeocdn.com and 2% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Dynatek.be.
Page size can be reduced by 858.6 kB (10%)
8.8 MB
7.9 MB
In fact, the total size of Dynatek.be main page is 8.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. 60% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.
Potential reduce by 24.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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 28% 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 24.1 kB or 81% of the original size.
Potential reduce by 119.4 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. Dynatek images are well optimized though.
Potential reduce by 460.1 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 460.1 kB or 69% of the original size.
Potential reduce by 255.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. Dynatek.be needs all CSS files to be minified and compressed as it can save up to 255.0 kB or 89% of the original size.
Number of requests can be reduced by 42 (54%)
78
36
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dynatek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
dynatek.be
292 ms
www.dynatek.be
734 ms
css
68 ms
master.css
87 ms
font-awesome.css
159 ms
animate.css
162 ms
icarousel.css
161 ms
adapt.js
164 ms
jquery-1.11.3.min.js
71 ms
jquery-ui.min.js
93 ms
froogaloop2.min.js
92 ms
modernizr.min.js
68 ms
waypoints.min.js
165 ms
jquery.bxslider.js
173 ms
impulsion.js
235 ms
jquery.fitvids.js
236 ms
jquery.mousewheel.js
234 ms
impMobileVeryLightbox.js
463 ms
jquery.easing.1.3.js
236 ms
raphael-min.js
327 ms
jquery.validate.js
254 ms
icarousel.min.js
307 ms
dynatek.js
308 ms
reset.css
234 ms
text.css
239 ms
1560.css
79 ms
fluiddesktop.css
84 ms
ga.js
24 ms
logo01en.png
164 ms
be.png
165 ms
nl.png
162 ms
de.png
162 ms
en.png
164 ms
at.png
163 ms
dz.png
233 ms
fr.png
231 ms
tw.png
232 ms
encart01-2.png
251 ms
encart02.png
231 ms
encart03.png
232 ms
encart04.png
380 ms
encart05.png
258 ms
encart06.png
259 ms
logo02en.png
259 ms
ribbonbuttonen.png
267 ms
piwik.js
542 ms
gtm.js
159 ms
147361980
161 ms
youtube2.png
400 ms
world2.png
368 ms
55ed8bedf37ce.jpg
893 ms
55ed7fbb79d6f.jpg
854 ms
55ed8b827219c.jpg
874 ms
563337ef942c8.jpg
911 ms
bgcc.png
447 ms
sprite01.png
479 ms
arrowdown01.png
524 ms
border01.png
559 ms
go3.png
602 ms
cloud.png
796 ms
IMG_9535.JPG
1976 ms
plus1.png
876 ms
T%C3%A9moignages4.jpg
1018 ms
VS.jpg
1298 ms
360.jpg
1352 ms
360.png
971 ms
sprite03.png
983 ms
__utm.gif
60 ms
Dosis-Regular-webfont.woff
909 ms
fontawesome-webfont.woff
923 ms
dosis-semibold-webfont.woff
957 ms
Dosis-Bold-webfont.woff
990 ms
dosis-extralight-webfont.woff
1001 ms
dosis-medium-webfont.woff
1037 ms
collect
120 ms
147361980
55 ms
fbds.js
4 ms
145 ms
player.js
51 ms
player.css
31 ms
ga.js
10 ms
vuid.min.js
41 ms
__utm.gif
23 ms
ga-audiences
92 ms
proxy.html
43 ms
546591966.jpg
134 ms
10018787_60x60.jpg
62 ms
21 ms
dynatek.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
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.
dynatek.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
Page has valid source maps
dynatek.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
Document doesn't have a valid hreflang
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dynatek.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 Dynatek.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.
dynatek.be
Open Graph description is not detected on the main page of Dynatek. 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: