7 sec in total
399 ms
5.8 sec
809 ms
Visit troyan.bg now to see the best up-to-date Troyan content for Bulgaria and also check out these interesting facts you probably never knew about troyan.bg
Община Троян
Visit troyan.bgWe analyzed Troyan.bg page load time and found that the first response time was 399 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.
troyan.bg performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value11.2 s
0/100
25%
Value18.1 s
0/100
10%
Value1,400 ms
16/100
30%
Value0.089
92/100
15%
Value11.9 s
16/100
10%
399 ms
1248 ms
403 ms
386 ms
746 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 80% of them (53 requests) were addressed to the original Troyan.bg, 8% (5 requests) were made to Gstatic.com and 6% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Troyan.bg.
Page size can be reduced by 114.3 kB (5%)
2.2 MB
2.0 MB
In fact, the total size of Troyan.bg main page is 2.2 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. 50% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 93.8 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 36.2 kB, which is 33% 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 93.8 kB or 86% of the original size.
Potential reduce by 17.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. Troyan 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 513 B
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. Troyan.bg has all CSS files already compressed.
Number of requests can be reduced by 18 (31%)
58
40
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Troyan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
troyan.bg
399 ms
www.troyan.bg
1248 ms
imagelightbox.min.css
403 ms
owl.carousel.css
386 ms
styles.css
746 ms
element.js
48 ms
api.js
40 ms
jquery.min.js
388 ms
popper.min.js
422 ms
bootstrap.min.js
649 ms
owl.carousel.min.js
732 ms
imagelightbox.min.js
696 ms
jquery.form.min.js
770 ms
jquery.validate.min.js
922 ms
scripts.js
989 ms
messages_bg.min.js
1032 ms
logo.png
622 ms
visit_troyan_medium.jpg
583 ms
mayor-menu.jpg
602 ms
hot-phones.jpg
921 ms
slider-image.jpg
1436 ms
thumb_izbori-20246.jpg
977 ms
thumb_e022a3cab8bfffc9b95e3679e60a7c7d.jpg
1009 ms
thumb_broshure-web-2024_1_page-0003.jpg
979 ms
thumb_izbori-20244.jpg
1083 ms
thumb_izbori-20243.jpg
1337 ms
thumb_plakat-2024-g.jpg
1583 ms
thumb_may.jpg
1366 ms
thumb_442694965_2252345141784938_5644953770402188489_n.jpg
1377 ms
thumb_talantlivi-deca-6.jpg
1656 ms
thumb_311935786_474576301366332_3154230017489872884_n.jpg
1853 ms
noimage.jpg
1749 ms
thumb_menyu-27_page-0001.jpg
2008 ms
thumb_e5ad9ba4-5b27-4e23-8e30-3a10c9b6b112.jpg
1942 ms
mayor-homepage.jpg
2055 ms
op2.jpg
2033 ms
op3.jpg
2123 ms
op4.jpg
1999 ms
op5.jpg
2299 ms
op6.jpg
2387 ms
op7.jpg
2513 ms
visit_troyan.jpg
2637 ms
vt_banner.jpg
2685 ms
agora.jpg
2512 ms
banner2.jpg
2774 ms
recaptcha__en.js
24 ms
roboto-v20-latin_cyrillic-regular.woff
2784 ms
roboto-v20-latin_cyrillic-700.woff
2882 ms
icomoon.ttf
2833 ms
banner3.jpg
2931 ms
banner4.jpg
2810 ms
banner5.jpg
2874 ms
anchor
356 ms
banner6.jpg
2812 ms
mun-activities-background.jpg
3012 ms
newslbackground.jpg
2813 ms
footer-background.jpg
3021 ms
styles__ltr.css
4 ms
recaptcha__en.js
13 ms
_SCkxxqdo6IitgoOo-OxNmiLhhkn12M3ougf1vTQFL8.js
35 ms
webworker.js
68 ms
logo_48.png
20 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
46 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
49 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
53 ms
recaptcha__en.js
32 ms
troyan.bg 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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.
troyan.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
troyan.bg 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
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 Troyan.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 Troyan.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.
troyan.bg
Open Graph data is detected on the main page of Troyan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: