7.2 sec in total
593 ms
6.3 sec
380 ms
Visit vum.bg now to see the best up-to-date Vum content for Bulgaria and also check out these interesting facts you probably never knew about vum.bg
VUM offers a huge variety of specialties suitable for your development! Register now at VU
Visit vum.bgWe analyzed Vum.bg page load time and found that the first response time was 593 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
vum.bg performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value32.4 s
0/100
25%
Value11.6 s
5/100
10%
Value2,490 ms
4/100
30%
Value0.041
99/100
15%
Value19.0 s
3/100
10%
593 ms
202 ms
327 ms
352 ms
349 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 79% of them (89 requests) were addressed to the original Vum.bg, 10% (11 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Vum.bg.
Page size can be reduced by 1.6 MB (15%)
10.4 MB
8.9 MB
In fact, the total size of Vum.bg main page is 10.4 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. Only a small number of websites need less resources to load. Images take 8.9 MB which makes up the majority of the site volume.
Potential reduce by 139.2 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 139.2 kB or 82% of the original size.
Potential reduce by 905.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. Vum images are well optimized though.
Potential reduce by 501.5 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 501.5 kB or 51% of the original size.
Potential reduce by 20.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. Vum.bg has all CSS files already compressed.
Number of requests can be reduced by 75 (80%)
94
19
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
vum.bg
593 ms
wp-emoji-release.min.js
202 ms
frontend-lite.min.css
327 ms
post-47218.css
352 ms
post-47529.css
349 ms
pa-frontend-c968aad59.min.css
363 ms
style.min.css
365 ms
classic-themes.min.css
368 ms
styles.css
470 ms
dashicons.min.css
584 ms
everest-forms.css
474 ms
style.min.css
493 ms
style.min.css
495 ms
cookieblocker.min.css
495 ms
css
31 ms
css
73 ms
bootstrap.css
526 ms
style.css
523 ms
default.css
545 ms
all.css
550 ms
dark.css
547 ms
swiper-bundle.css
633 ms
jquery.smartmenus.bootstrap.css
646 ms
animate.css
655 ms
ekiticons.css
679 ms
elementor-icons.min.css
677 ms
swiper.min.css
688 ms
post-27.css
757 ms
global.css
776 ms
post-90.css
776 ms
font-awesome.min.css
806 ms
popupaoc-public.css
808 ms
widget-styles.css
942 ms
responsive.css
880 ms
fontawesome.min.css
902 ms
solid.min.css
897 ms
brands.min.css
933 ms
smartslider.min.css
933 ms
css
26 ms
widget-icon-list.min.css
999 ms
all.min.css
900 ms
slick.min.css
772 ms
language-cookie.js
796 ms
jquery.min.js
912 ms
jquery-migrate.min.js
785 ms
navigation.js
835 ms
bootstrap.js
860 ms
swiper-bundle.js
879 ms
main.js
797 ms
sticksy.min.js
785 ms
jquery.smartmenus.js
833 ms
jquery.smartmenus.bootstrap.js
863 ms
n2.min.js
927 ms
smartslider-frontend.min.js
944 ms
ss-simple.min.js
935 ms
pa-frontend-c968aad59.min.js
921 ms
popupaoc-public.js
920 ms
frontend-script.js
916 ms
widget-scripts.js
835 ms
complianz.min.js
988 ms
jquery-numerator.min.js
976 ms
imagesloaded.min.js
955 ms
isotope.min.js
947 ms
slick.min.js
946 ms
custom.js
1167 ms
webpack.runtime.min.js
1177 ms
frontend-modules.min.js
1144 ms
waypoints.min.js
1142 ms
core.min.js
1072 ms
frontend.min.js
1054 ms
animate-circle.min.js
1066 ms
elementor.js
1035 ms
UAoZWuNRjRM
236 ms
vum-logo-header-EN-q0636uhtq3pafe9djr7f20ky4nivn32n30kbfk1kw0.png
639 ms
bg.png
639 ms
en.png
639 ms
MG_1228-1-scaled.jpg
981 ms
U-Multirank-Button_U-Symbol-300x277.png
792 ms
logo.png
791 ms
CAMPUSES-1024x1024.png
1433 ms
POST3-PICNIC-1024x1024.png
1348 ms
ERASMUS-1024x1024.png
1431 ms
21.png
1815 ms
WELLCOME-14.png
1438 ms
DSC_0044-scaled.jpg
1228 ms
vum-logo-footer-EN-q06352kstd9shwu7wzkscgplqg9x3o0w687asqocn4.png
1351 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFWUUwdYPFkaVN.ttf
50 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFWUUwdYPFkaVN.ttf
90 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FWUUwdYPFkaVN.ttf
192 ms
fa-solid-900.woff
1350 ms
fa-solid-900.woff
2313 ms
fa-regular-400.woff
1430 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
109 ms
KFOmCnqEu92Fr1Mu7GxPKTU1Kg.ttf
109 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
89 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMhhKibpUVz0Eg.ttf
193 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ArQbMhhKibpUVz0Eg.ttf
168 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMhhKibpUVz0Eg.ttf
167 ms
elementskit.woff
1479 ms
fa-brands-400.woff
1446 ms
fa-brands-400.woff
1480 ms
www-player.css
24 ms
www-embed-player.js
84 ms
base.js
107 ms
ad_status.js
234 ms
XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js
154 ms
embed.js
81 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
48 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
48 ms
id
27 ms
Create
76 ms
GenerateIT
16 ms
fa-solid-900.ttf
136 ms
vum.bg accessibility score
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
vum.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
vum.bg 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vum.bg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Vum.bg 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.
vum.bg
Open Graph data is detected on the main page of Vum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: