7.1 sec in total
935 ms
5.1 sec
1 sec
Visit tu-sofia.bg now to see the best up-to-date Tu Sofia content for Bulgaria and also check out these interesting facts you probably never knew about tu-sofia.bg
Visit tu-sofia.bgWe analyzed Tu-sofia.bg page load time and found that the first response time was 935 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
tu-sofia.bg performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value7.1 s
5/100
25%
Value7.5 s
26/100
10%
Value700 ms
42/100
30%
Value0
100/100
15%
Value10.6 s
23/100
10%
935 ms
399 ms
270 ms
285 ms
284 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 97% of them (66 requests) were addressed to the original Tu-sofia.bg, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Tu-sofia.bg.
Page size can be reduced by 869.1 kB (29%)
3.0 MB
2.2 MB
In fact, the total size of Tu-sofia.bg 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. 40% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 31.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. This page needs HTML code to be minified as it can gain 10.0 kB, which is 27% 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 31.0 kB or 83% of the original size.
Potential reduce by 102.2 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. Tu Sofia images are well optimized though.
Potential reduce by 680.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 680.4 kB or 74% of the original size.
Potential reduce by 55.5 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. Tu-sofia.bg needs all CSS files to be minified and compressed as it can save up to 55.5 kB or 81% of the original size.
Number of requests can be reduced by 19 (28%)
67
48
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tu Sofia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
tu-sofia.bg
935 ms
layout_and_backgrounds.css
399 ms
navigation.css
270 ms
form.css
285 ms
main.css
284 ms
website.css
286 ms
style_admin.css
314 ms
sliders.css
400 ms
bootstrap.min.css
423 ms
style_slideshow.css
421 ms
jquery-1.5.1rc1.js
1269 ms
news_tab.js
450 ms
sliders.js
528 ms
jquery-ui.min.js
1184 ms
ckeditor.js
1802 ms
analytics.js
344 ms
body_bgr.png
1418 ms
shadow_bottom_new.png
161 ms
TU_Logo_Mery.png
157 ms
site_map_icon.png
184 ms
contacts_icon.png
164 ms
search_icon.png
157 ms
login_icon.png
264 ms
lang_icon.png
259 ms
blue-lt-curve.png
273 ms
blue-nav-bg.png
273 ms
blue-rt-curve.png
276 ms
shadow_new_bgr.png
389 ms
selected-item.gif
388 ms
15february.jpg
402 ms
KSK_2016_v2.jpg
400 ms
Diplom_v3.jpg
407 ms
ECAD_SMARTCOM.jpg
507 ms
Aviation.jpg
506 ms
Pilots_v2.jpg
536 ms
15february.jpg
1515 ms
transparent-bg.png
541 ms
KSK_2016_v2.jpg
1286 ms
Diplom_v3.jpg
1418 ms
ECAD_SMARTCOM.jpg
943 ms
Aviation.jpg
1521 ms
Pilots_v2.jpg
1220 ms
title_round_bgr_part1.png
1359 ms
12_future_students_img.jpg
1415 ms
separator.png
1497 ms
read-more.png
1507 ms
13_students_img.jpg
1543 ms
Quicklink-symbol.png
1544 ms
16_education_img.jpg
1630 ms
title_round_gradient_bgr_left.png
1635 ms
event_date_bgr.png
1640 ms
arrow_go_bottom.png
1649 ms
collect
40 ms
arrow_go_top.png
1558 ms
Library_banner.jpg
1553 ms
TA_banner_.jpg
1647 ms
transparent_bgr.png
1636 ms
slide_left_btn_dark.jpg
1638 ms
CMKT-Jivo.gif
1570 ms
logo3-bg.jpg
1579 ms
alumni-baner-bg.jpg
1565 ms
logo_InfoCenter.png
1674 ms
logo_izdatel.png
1676 ms
TA_banner.png
1563 ms
careers.jpg
1580 ms
slide_right_btn_dark.jpg
1560 ms
footer_bgr.jpg
1557 ms
footer_slide_up_btn.jpg
1665 ms
tu-sofia.bg 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.
tu-sofia.bg 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
tu-sofia.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 doesn't use legible font sizes
Tap targets are not sized appropriately
BG
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tu-sofia.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it does not match the claimed English language. Our system also found out that Tu-sofia.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.
tu-sofia.bg
Open Graph description is not detected on the main page of Tu Sofia. 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: