2.7 sec in total
247 ms
2.3 sec
201 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 247 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
epicframe.be performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value25.4 s
0/100
25%
Value23.1 s
0/100
10%
Value5,690 ms
0/100
30%
Value0.05
99/100
15%
Value41.1 s
0/100
10%
247 ms
45 ms
51 ms
42 ms
55 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 44% of them (48 requests) were addressed to the original Epicframe.be, 13% (14 requests) were made to Fonts.gstatic.com and 13% (14 requests) were made to App-3qnov074as.marketingautomation.services. The less responsive or slowest element that took the longest time to load (964 ms) relates to the external source App3.salesmanago.pl.
Page size can be reduced by 759.5 kB (26%)
3.0 MB
2.2 MB
In fact, the total size of Epicframe.be main page is 3.0 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 75.7 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 75.7 kB or 78% of the original size.
Potential reduce by 170.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, Epic Frame needs image optimization as it can save up to 170.1 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 58.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. This website has mostly compressed JavaScripts.
Potential reduce by 455.7 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 455.7 kB or 77% of the original size.
Number of requests can be reduced by 73 (88%)
83
10
The browser has sent 83 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 51 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
epicframe.be
247 ms
wp-emoji-release.min.js
45 ms
style.min.css
51 ms
classic-themes.min.css
42 ms
cleantalk-public.min.css
55 ms
frontend.css
47 ms
responsive.css
53 ms
style.css
73 ms
magnific-popup.css
81 ms
wfml-custom.css
73 ms
email-before-download-public.css
78 ms
app.css
89 ms
style.css
106 ms
css
47 ms
css
63 ms
js_composer.min.css
119 ms
jquery-3.6.3.min.js
109 ms
jquery-migrate-3.4.0.min.js
112 ms
apbct-public-bundle.min.js
151 ms
gambit-smoothscroll-min.js
117 ms
ebm6byl.js
87 ms
82854.js
113 ms
form.js
149 ms
style.css
169 ms
animate.min.css
169 ms
rs6.css
176 ms
frontend-min.js
173 ms
script.min.js
173 ms
rbtools.min.js
174 ms
rs6.min.js
174 ms
page-preloader.js
174 ms
jquery.magnific-popup.min.1.0.1.js
236 ms
wfml-init.js
238 ms
dlm-xhr.min.js
239 ms
gtm4wp-form-move-tracker.js
238 ms
player.js
40 ms
gtm4wp-vimeo.js
238 ms
email-before-download-public.js
238 ms
main.js
279 ms
vendor.min.js
285 ms
underscore.min.js
274 ms
app.min.js
283 ms
js_composer_front.min.js
239 ms
script-min.js
236 ms
masonry.pkgd.min.js
340 ms
imagesloaded.pkgd.min.js
335 ms
vc-waypoints.min.js
334 ms
vc_grid.min.js
333 ms
ss.js
83 ms
gtm.js
199 ms
hotjar-1347459.js
226 ms
336574327
220 ms
preloader.gif
216 ms
Logo-website_reverse.gif
219 ms
logo.png
320 ms
homepage-video-1.png
341 ms
arrow.png
320 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaHUlP.ttf
24 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf
28 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaHUlP.ttf
38 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDypqaE0lP.ttf
52 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaHUlP.ttf
54 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDppqaE0lP.ttf
52 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaHUlP.ttf
104 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJqaE0lP.ttf
51 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aHUlP.ttf
51 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lP.ttf
121 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aHUlP.ttf
121 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDH52aE0lP.ttf
121 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aHUlP.ttf
121 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDeJ2aE0lP.ttf
120 ms
fontawesome-webfont.woff
325 ms
koi
152 ms
api.js
116 ms
sm.js
964 ms
336574327
137 ms
d
14 ms
d
19 ms
d
31 ms
d
31 ms
d
30 ms
d
31 ms
MzUwNbFMTEnSNUozMdI1SUtJ1k0ySzPVNTExMk41tjRJsrBIBgA
103 ms
p.gif
48 ms
formbasics.css
42 ms
jquery-ui.min.css
52 ms
base.css
63 ms
datetimepicker.css
54 ms
jquery-3.6.0.min.js
70 ms
jquery.validate.min.js
121 ms
additional-methods.min.js
68 ms
jquery.form.js
83 ms
jquery-ui.min.js
83 ms
datetimepicker.js
144 ms
jquery.placeholder.js
114 ms
api.js
46 ms
messages_nl_NL.js
114 ms
conditional-form-fields.js
148 ms
getChatbot
224 ms
api.js
12 ms
recaptcha__en.js
27 ms
publicChatbot
46 ms
polyfill.min.js
52 ms
en.js
23 ms
antd.css
35 ms
en_US.main.css
34 ms
en_US.main.js
119 ms
css
25 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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: