12.3 sec in total
617 ms
11 sec
685 ms
Click here to check amazing Onfire content for Bulgaria. Otherwise, check out these important facts you probably never knew about onfire.bg
Портал за почивки и пътуване в България и чужбина
Visit onfire.bgWe analyzed Onfire.bg page load time and found that the first response time was 617 ms and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
onfire.bg performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value6.3 s
10/100
25%
Value6.7 s
36/100
10%
Value440 ms
64/100
30%
Value0.606
10/100
15%
Value9.2 s
32/100
10%
617 ms
806 ms
122 ms
363 ms
429 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 77% of them (83 requests) were addressed to the original Onfire.bg, 5% (5 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Onfire.bg.
Page size can be reduced by 2.7 MB (23%)
12.1 MB
9.3 MB
In fact, the total size of Onfire.bg main page is 12.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. 65% of websites need less resources to load. Images take 9.8 MB which makes up the majority of the site volume.
Potential reduce by 453.3 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 453.3 kB or 90% of the original size.
Potential reduce by 979.0 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. Onfire images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 76% of the original size.
Potential reduce by 197.2 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. Onfire.bg needs all CSS files to be minified and compressed as it can save up to 197.2 kB or 85% of the original size.
Number of requests can be reduced by 33 (35%)
94
61
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Onfire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
onfire.bg
617 ms
806 ms
css
122 ms
jquery-ui.css
363 ms
slick.css
429 ms
jquery.selectBoxIt.css
434 ms
introjs.css
431 ms
styles.css
434 ms
style.css
208 ms
animate.min.css
424 ms
perfect-scrollbar-0.4.6.min.css
432 ms
js
72 ms
respond.min.js
458 ms
jquery.min.js
755 ms
jquery-ui.min.js
1009 ms
jquery.ui.touch-punch.js
654 ms
slick.min.js
652 ms
jquery.countdown.min.js
656 ms
jquery.selectBoxIt.min.js
703 ms
intro.min.js
815 ms
readmore.min.js
852 ms
init.js
855 ms
old.init.js
866 ms
conversion.js
57 ms
perfect-scrollbar-0.4.6.with-mousewheel.min.js
481 ms
ulp-jsonp.js
483 ms
Fl4y0QdOxyyTHEGMXX8kcT8E0i7KZn-EPnyo3HZu7kw.woff
665 ms
Y5yuUJGDLtmYv2_3fMB4fA.woff
694 ms
oHi30kwQWvpCWqAhzHcCSD8E0i7KZn-EPnyo3HZu7kw.woff
780 ms
isZ-wbCXNKAbnjo6_TwHTj8E0i7KZn-EPnyo3HZu7kw.woff
848 ms
3Y_xCyt7TNunMGg0Et2pnj8E0i7KZn-EPnyo3HZu7kw.woff
848 ms
logo@2x.png
536 ms
C_9622d787300bf2487fb2753b8c5225ae.jpg
3170 ms
C_b7fa29bf27b451237c3cd8ad99e1be7e.jpg
5489 ms
C_7376bc21c7f8b91386e86452fd1c47b9.jpg
3533 ms
B_9622d787300bf2487fb2753b8c5225ae.jpg
588 ms
B_b7fa29bf27b451237c3cd8ad99e1be7e.jpg
567 ms
B_7376bc21c7f8b91386e86452fd1c47b9.jpg
746 ms
default-1024x1024.jpg
869 ms
e2bc77db2e3a066df594c55f509d6614.jpg
1232 ms
transperant-960x405.png
994 ms
default-960x405.jpg
1223 ms
sprite.png
2169 ms
fbevents.js
481 ms
analytics.js
389 ms
471 ms
iconsFont.ttf
1307 ms
watch.js
1 ms
hotjar-138722.js
462 ms
ajax.php
1985 ms
ui-bg_flat_75_ffffff_40x100.png
961 ms
F_e3796ca91425d9f3eb02291ad2c89a2e.jpg
1700 ms
F_9fe681663bd11a135415443762782545.jpg
2371 ms
F_35714668941e3104255ff3270d1e88e5.jpg
2329 ms
F_ddccf60cc996402cdda19dc308645df8.jpg
2334 ms
F_c56402d8a7c327b276f1fa4110bd5e2f.jpg
2992 ms
F_b7498cb76f9d7a5a08a0137e17acebf3.jpg
2949 ms
B_0f32d0c8e09c0809a6bda97864a3d75c.jpg
5592 ms
G_e6a0368211f635167440ce358d24419b.jpg
3304 ms
G_c67af8485d1c0108c8d14e3fac00a603.jpg
3831 ms
G_ce995760677cb09e2286c482a53682a2.jpg
3888 ms
G_dd1484b992615536a9be28d10ca6f994.jpg
3671 ms
G_048404cc6d3c4ca78e68969889714953.jpg
3908 ms
G_9cbf595a9bd86f9d4e41966cbc362c6d.jpg
4189 ms
G_eeddd85df39d3f498fc2a1ff357b1dad.jpg
4545 ms
G_314cc45866e7e35d9c3e04af20a8bafb.jpg
5124 ms
G_cb35410c8b3c2f914b9394988f17c118.jpg
5499 ms
G_d1d3a9fcf70d056145bbb935fb2d8536.jpg
5591 ms
G_8c68201b21279f665ce97cf786595d12.jpg
5171 ms
G_949bca2810e5beb13d2f16abb4e662c4.jpg
5502 ms
G_464654413331826718e0c59d8910ea0a.jpg
5819 ms
G_91f014ad8f08d543476cad32ca81b2c4.jpg
6369 ms
G_a446423b1a0f4905d135f47dd8984d4c.jpg
6098 ms
collect
53 ms
223 ms
modules-79ac3e471402dedc7fa595a0b4974f10.js
285 ms
235 ms
collect
270 ms
ga-audiences
29 ms
font-awesome.min.css
307 ms
css
31 ms
popupbg.jpg
4221 ms
pool.jpg
4013 ms
sticker.png
3826 ms
bg.jpg
4357 ms
sticker.png
4012 ms
bg.jpg
4182 ms
logo.png
4178 ms
star.png
4268 ms
mountain.png
4343 ms
spa.png
4344 ms
macbookpro.png
1200 ms
pointer01.png
320 ms
macbook.png
1568 ms
business03.jpg
938 ms
finance.png
588 ms
red-ribbon.png
676 ms
city.jpg
1455 ms
green-ribbon.png
888 ms
bubbles.png
1458 ms
bubbles2.png
1557 ms
medite-popup.jpg
1461 ms
medite-popup.jpg
3113 ms
common.js
10 ms
util.js
28 ms
stats.js
9 ms
AuthenticationService.Authenticate
273 ms
380 ms
onfire.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.
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
onfire.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
onfire.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 Onfire.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 Onfire.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.
onfire.bg
Open Graph description is not detected on the main page of Onfire. 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: