5.8 sec in total
677 ms
4.8 sec
316 ms
Click here to check amazing Epic Frame content. Otherwise, check out these important facts you probably never knew about epicframe.be
Zet je bedrijf, merk of product in de kijker met videoproductie of animatievideos! Wij realiseren je idee van concept tot een afgewerkt eindproduct.
Visit epicframe.beWe analyzed Epicframe.be page load time and found that the first response time was 677 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
epicframe.be performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value39.1 s
0/100
25%
Value46.8 s
0/100
10%
Value58,270 ms
0/100
30%
Value0.146
77/100
15%
Value76.6 s
0/100
10%
677 ms
337 ms
198 ms
134 ms
212 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 40% of them (53 requests) were addressed to the original Epicframe.be, 10% (13 requests) were made to App-3qnov074as.marketingautomation.services and 9% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Epicframe.be.
Page size can be reduced by 691.0 kB (26%)
2.7 MB
2.0 MB
In fact, the total size of Epicframe.be main page is 2.7 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. 85% 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 78.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 78.1 kB or 77% of the original size.
Potential reduce by 170.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. Epic Frame images are well optimized though.
Potential reduce by 48.0 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 48.0 kB or 19% of the original size.
Potential reduce by 395.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. Epicframe.be needs all CSS files to be minified and compressed as it can save up to 395.0 kB or 71% of the original size.
Number of requests can be reduced by 80 (73%)
109
29
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epic Frame. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
epicframe.be
677 ms
wp-emoji-release.min.js
337 ms
style.min.css
198 ms
frontend.css
134 ms
responsive.css
212 ms
styles.css
206 ms
email-before-download-public.css
220 ms
style.css
190 ms
settings.css
231 ms
magnific-popup.css
237 ms
wfml-custom.css
249 ms
frontend.css
253 ms
app.css
273 ms
style.css
322 ms
css
168 ms
css
188 ms
js_composer.min.css
335 ms
jquery.js
326 ms
jquery-migrate.min.js
328 ms
apbct-public.min.js
328 ms
cleantalk_nocache.min.js
333 ms
jquery.themepunch.tools.min.js
473 ms
jquery.themepunch.revolution.min.js
496 ms
gambit-smoothscroll-min.js
496 ms
gtm4wp-form-move-tracker.js
497 ms
player.js
143 ms
gtm4wp-vimeo.js
619 ms
ebm6byl.js
324 ms
82854.js
180 ms
form.js
222 ms
style.css
483 ms
frontend-min.js
732 ms
scripts.js
486 ms
email-before-download-public.js
483 ms
script.min.js
484 ms
jquery.magnific-popup.min.1.0.1.js
486 ms
wfml-init.js
487 ms
main.js
488 ms
vendor.min.js
489 ms
underscore.min.js
499 ms
app.min.js
502 ms
wp-embed.min.js
495 ms
js_composer_front.min.js
390 ms
script-min.js
348 ms
ss.js
128 ms
gtm.js
258 ms
hotjar-1347459.js
592 ms
336574327
247 ms
preloader.gif
592 ms
Logo-website_reverse.gif
989 ms
homepage-video-1.png
1287 ms
Thumbnail_ERAP.jpg
600 ms
GrootteThumbnail_MotmansPartners.jpg
709 ms
Thumbnail_P4A.jpg
598 ms
Thumbnail_lecoque.jpg
1147 ms
Thumbnail_Bosal.jpg
1246 ms
Thumbnail_VanBreda.jpg
1145 ms
GrootteThumbnail_SintVeroonMars.jpg
1046 ms
Thumbnail_Elini.jpg
1180 ms
Thumbnail_SafetyFirstInfrabel.jpg
1175 ms
Thumbnail_Crius.jpg
1727 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaHUlM.woff
141 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lM.woff
321 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaHUlM.woff
505 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaE0lM.woff
511 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaHUlM.woff
621 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaE0lM.woff
622 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaHUlM.woff
620 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aHUlM.woff
510 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lM.woff
622 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aHUlM.woff
657 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lM.woff
657 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aHUlM.woff
898 ms
arrow.png
1589 ms
player.js
119 ms
player.css
118 ms
vuid.min.js
118 ms
fontawesome-webfont.woff
1493 ms
sm.js
1637 ms
336574327
370 ms
koi
528 ms
d
163 ms
d
443 ms
d
443 ms
d
498 ms
d
497 ms
d
442 ms
analytics.js
532 ms
insight.min.js
624 ms
hotjar-1347459.js
185 ms
3405416.js
616 ms
fbevents.js
518 ms
16921ded097d49d2b7bbe971bc4395ee.js.ubembed.com
752 ms
ping.js
664 ms
hotjar-2717404.js
512 ms
js
208 ms
modules.61e17720cf639c3e96a7.js
706 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
554 ms
player.js
597 ms
player.css
509 ms
vuid.min.js
590 ms
p.gif
656 ms
collect
175 ms
1858334837792939
594 ms
getChatbot
589 ms
MzUwNbFMTEnSNUozMdI1SUtJ1k0ySzPVNTExMk41tjRJsrBIBgA
502 ms
collect
643 ms
bundle.js
579 ms
formbasics.css
515 ms
jquery-ui.min.css
550 ms
base.css
538 ms
datetimepicker.css
558 ms
jquery-3.6.0.min.js
656 ms
jquery.validate.min.js
655 ms
additional-methods.min.js
674 ms
jquery.form.js
674 ms
jquery-ui.min.js
691 ms
datetimepicker.js
681 ms
jquery.placeholder.js
688 ms
api.js
653 ms
messages_nl_NL.js
688 ms
783451912-bbd0341a092ec4ad8a6db26cd10359212047cfb795423885da3887ac7c74d5ee-d
922 ms
visit-data
568 ms
publicChatbot
204 ms
ga-audiences
116 ms
polyfill.min.js
123 ms
en.js
121 ms
antd.css
259 ms
en_US.main.css
489 ms
en_US.main.js
293 ms
recaptcha__en.js
252 ms
18 ms
css
15 ms
epicframe.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.
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
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.
epicframe.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
epicframe.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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epicframe.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 Epicframe.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.
epicframe.be
Open Graph data is detected on the main page of Epic Frame. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: