3.6 sec in total
403 ms
2.8 sec
458 ms
Click here to check amazing Epilion content for Serbia. Otherwise, check out these important facts you probably never knew about epilion.rs
Najduže iskustvo sa dermatološkim laserima i kontinuirana primena najviših standarda u radu sa pacijentima.
Visit epilion.rsWe analyzed Epilion.rs page load time and found that the first response time was 403 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 60% of websites can load faster.
epilion.rs performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value9.6 s
0/100
25%
Value9.7 s
11/100
10%
Value4,470 ms
0/100
30%
Value0.01
100/100
15%
Value17.1 s
4/100
10%
403 ms
1078 ms
594 ms
198 ms
297 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 68% of them (40 requests) were addressed to the original Epilion.rs, 8% (5 requests) were made to Googletagmanager.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Epilion.rs.
Page size can be reduced by 127.0 kB (12%)
1.1 MB
952.6 kB
In fact, the total size of Epilion.rs main page is 1.1 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. 70% of websites need less resources to load. Javascripts take 451.3 kB which makes up the majority of the site volume.
Potential reduce by 84.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 84.0 kB or 79% of the original size.
Potential reduce by 4.3 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. Epilion images are well optimized though.
Potential reduce by 2.4 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 36.3 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. Epilion.rs needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 18% of the original size.
Number of requests can be reduced by 40 (78%)
51
11
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epilion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
epilion.rs
403 ms
epilion.rs
1078 ms
mtc.js
594 ms
style.min.css
198 ms
styles.css
297 ms
cookie-law-info-public.css
296 ms
cookie-law-info-gdpr.css
296 ms
font-awesome.min.css
298 ms
genericons.css
399 ms
front-end.css
303 ms
dashicons.min.css
495 ms
style.css
603 ms
style.css
406 ms
css
43 ms
jquery.min.js
504 ms
jquery-migrate.min.js
407 ms
cookie-law-info-public.js
508 ms
frontend.js
530 ms
wpp.min.js
512 ms
es6-promise.auto.min.js
654 ms
recaptcha.js
656 ms
js
73 ms
css
57 ms
font-awesome.min.css
37 ms
js
44 ms
et-core-unified-2-17143792794684.min.css
567 ms
index.js
567 ms
index.js
606 ms
custom.unified.js
875 ms
wpfront-scroll-top.min.js
719 ms
common.js
719 ms
api.js
58 ms
wp-polyfill-inert.min.js
718 ms
regenerator-runtime.min.js
718 ms
wp-polyfill.min.js
717 ms
index.js
971 ms
smush-lazy-load.min.js
971 ms
fbevents.js
152 ms
gtm.js
137 ms
home-1-1920x1080.jpg
391 ms
iStock-960998912-1920x1080-1.jpg
390 ms
home-2-1920x1080.jpg
389 ms
home-2-1920x1080-1024x576.jpg
392 ms
home-4-1920x1080.jpg
679 ms
js
257 ms
analytics.js
251 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
250 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
377 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
400 ms
modules.ttf
526 ms
fontawesome-webfont.woff
83 ms
fontawesome-webfont.woff
524 ms
mautic-form.js
472 ms
facebook-icon.png
318 ms
instagram-icon.png
316 ms
destination
277 ms
recaptcha__en.js
252 ms
Logo.png
166 ms
collect
97 ms
epilion.rs 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.
epilion.rs best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
epilion.rs 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
SR
SR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epilion.rs can be misinterpreted by Google and other search engines. Our service has detected that Serbian is used on the page, and it matches the claimed language. Our system also found out that Epilion.rs 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.
epilion.rs
Open Graph data is detected on the main page of Epilion. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: