5.9 sec in total
1.6 sec
4 sec
335 ms
Visit navet.government.bg now to see the best up-to-date Navet Government content for Bulgaria and also check out these interesting facts you probably never knew about navet.government.bg
Visit navet.government.bgWe analyzed Navet.government.bg page load time and found that the first response time was 1.6 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
navet.government.bg performance score
name
value
score
weighting
Value3.4 s
39/100
10%
Value3.4 s
68/100
25%
Value5.0 s
63/100
10%
Value90 ms
99/100
30%
Value0.003
100/100
15%
Value5.0 s
76/100
10%
1616 ms
18 ms
278 ms
282 ms
285 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 86% of them (54 requests) were addressed to the original Navet.government.bg, 5% (3 requests) were made to Ajax.googleapis.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.6 sec) belongs to the original domain Navet.government.bg.
Page size can be reduced by 463.6 kB (55%)
842.2 kB
378.6 kB
In fact, the total size of Navet.government.bg main page is 842.2 kB. 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. Javascripts take 270.2 kB which makes up the majority of the site volume.
Potential reduce by 142.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 142.2 kB or 87% of the original size.
Potential reduce by 10.6 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. Navet Government images are well optimized though.
Potential reduce by 181.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 181.4 kB or 67% of the original size.
Potential reduce by 129.4 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. Navet.government.bg needs all CSS files to be minified and compressed as it can save up to 129.4 kB or 75% of the original size.
Number of requests can be reduced by 36 (63%)
57
21
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Navet Government. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.navet.government.bg
1616 ms
jquery-ui.css
18 ms
gg_event_styles.css
278 ms
wpa-style.css
282 ms
a11y-toolbar.css
285 ms
a11y.css
289 ms
a11y-fontsize.css
285 ms
wprmenu.css
379 ms
css
26 ms
genericons.css
550 ms
style.css
422 ms
app.css
428 ms
ubermenu.min.css
429 ms
font-awesome.min.css
432 ms
custom.css
505 ms
jquery.js
706 ms
jquery-migrate.min.js
569 ms
jquery.mousewheel.js
567 ms
core.min.js
569 ms
datepicker.min.js
634 ms
gg_script.js
684 ms
jquery.transit.min.js
745 ms
jquery.sidr.js
748 ms
wprmenu.js
749 ms
is_wsi.css
650 ms
is_wsi.js
707 ms
jquery.scrollto.min.js
692 ms
a11y.js
695 ms
longdesc.button.js
694 ms
functions.js
695 ms
ubermenu.min.js
698 ms
custom.js
722 ms
analytics.js
112 ms
bkgr22b.png
283 ms
logo-navet.png
288 ms
home-s.png
181 ms
smap-sm.png
180 ms
cont-s.png
178 ms
fb-s.png
249 ms
search1.png
271 ms
bl5.png
427 ms
appl.jpg
289 ms
cvt3.jpg
354 ms
looking.jpg
397 ms
docs.jpg
420 ms
0-90x60.jpg
427 ms
Prilozhenie-3-2-90x60.jpg
430 ms
ecvet-widget-240x180.jpg
491 ms
EQAVET_logo250.jpg
525 ms
eqf1.jpg
561 ms
epale_horizontal_static-1.png
566 ms
logo-da-240x174.png
567 ms
opac-bg.png
572 ms
ajax-loader.gif
626 ms
top-t.png
653 ms
fontawesome-webfont.woff
785 ms
collect
92 ms
ui-bg_flat_75_ffffff_40x100.png
73 ms
ui-icons_222222_256x240.png
32 ms
a11y-toolbar.woff
541 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
8 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
9 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
29 ms
navet.government.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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
navet.government.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
navet.government.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
Tap targets are not sized appropriately
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Navet.government.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Navet.government.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.
navet.government.bg
Open Graph description is not detected on the main page of Navet Government. 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: