4.7 sec in total
473 ms
3.7 sec
516 ms
Click here to check amazing Fratelli content for Bulgaria. Otherwise, check out these important facts you probably never knew about fratelli.bg
Уникални рецепти! Доставка на пици, доставка на храна и обедно меню до дома във Варна. Паста, свежи салати, интересни предястия, пареща скара и любими десерти.
Visit fratelli.bgWe analyzed Fratelli.bg page load time and found that the first response time was 473 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fratelli.bg performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value25.3 s
0/100
25%
Value6.7 s
36/100
10%
Value360 ms
72/100
30%
Value0.205
60/100
15%
Value7.5 s
48/100
10%
473 ms
677 ms
50 ms
101 ms
236 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 90% of them (92 requests) were addressed to the original Fratelli.bg, 6% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fratelli.bg.
Page size can be reduced by 489.6 kB (6%)
8.2 MB
7.7 MB
In fact, the total size of Fratelli.bg main page is 8.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. 65% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.
Potential reduce by 78.6 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 78.6 kB or 84% of the original size.
Potential reduce by 341.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. Fratelli images are well optimized though.
Potential reduce by 59.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 59.4 kB or 26% of the original size.
Potential reduce by 10.0 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. Fratelli.bg needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 14% of the original size.
Number of requests can be reduced by 37 (40%)
93
56
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fratelli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
fratelli.bg
473 ms
fratelli.bg
677 ms
js
50 ms
js
101 ms
font-awesome.css
236 ms
css
36 ms
bootstrap.css
453 ms
style.css
462 ms
jquery.fancybox.min.css
341 ms
carousel.css
356 ms
custom.css
354 ms
animate.css
354 ms
layerslider.css
460 ms
owl.carousel.css
476 ms
owl.transitions.css
477 ms
logo.png
621 ms
s_5f4de73f78e5a_4f72d8bddb29c.png
1259 ms
m_5f4de73f78e5a_23196934d3366.png
1151 ms
r_6532478b5cff9_a9298e65315d2.png
928 ms
r_6532478b5cff9_614aca1fc1a2f.png
943 ms
r_63cfdaeb8f29c_b647188d0984f.png
1169 ms
r_63569970b8efb_e9a79b5e99a4f.png
1057 ms
r_63cfdfc2b0108_a849f51aa744b.png
1153 ms
r_5db6f2b364ea3_b8b67bdf5988d.png
1062 ms
r_6532472731392_cfdca6a9522a1.png
1292 ms
r_63cfe0c9cb7a8_3566aee2715b6.png
1182 ms
r_5f8195bb1d99a_74212c8e239af.png
1264 ms
r_60a5111ca7bc7_c852be49a36b4.png
1265 ms
r_60a51af840cb3_a06daebda48a1.png
1403 ms
r_5db6f42d44f43_a123ce7ca0da3.png
1302 ms
r_60a5119d73d62_dde19e6d766a3.png
1371 ms
r_647e44ae52af3_fd60fdb8ec8f5.png
1376 ms
r_5ca893c3871f6_44e1aaf7c90bf.png
1376 ms
r_653246467e1a3_57fd910fe1182.jpg
1408 ms
r_5ca8943e423c6_92c7d49142750.png
1419 ms
r_60a4f89372c16_e3bcd474cc2b2.png
1482 ms
r_61580d16d6539_def0c299c7a44.png
1488 ms
r_61580d9ee702e_36612fe399d62.png
1489 ms
r_5f818e9196b98_52b0031a6cd2b.png
1518 ms
jquery-2.1.1.js
1424 ms
bootstrap.min.2.3.2.js
1437 ms
jquery.easing.js
1366 ms
jquery.fancybox.min.js
1269 ms
jquery.validate.js
1261 ms
messages_bg.js
1289 ms
jquery.matchHeight.js
1300 ms
device.min.js
1206 ms
stickUp.js
1238 ms
custom.js
1248 ms
slick.js
1214 ms
jstree.min.js
1137 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
19 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
27 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
87 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
95 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
95 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
95 ms
carousel.min.js
1150 ms
pixo.min.js
852 ms
jquery.custom.min.js
879 ms
common.js
777 ms
gwebd.js
776 ms
functions.js
727 ms
actions.js
738 ms
greensock.js
733 ms
layerslider.transitions.js
751 ms
layerslider.kreaturamedia.jquery.js
689 ms
owl.carousel.min.js
691 ms
cookieconsent.js
728 ms
fontawesome-webfont.woff
844 ms
header-icon.png
835 ms
service-1.png
766 ms
service-3.png
760 ms
service-2.png
759 ms
arrow.png
735 ms
top_categories.jpg
728 ms
effect.png
726 ms
c_5c87a51786d21_c095f62d4119a.jpg
674 ms
c_5db6eb52bda0d_9c4b182428a4d.jpg
683 ms
c_5c93b852d0929_4351b8688aa88.jpg
685 ms
c_5c8a468090dee_cb92fc8eaaaa9.jpg
707 ms
c_5bf6c8ad5f3cd_f14a036ef3acb.jpg
703 ms
c_5c8a47416bb81_3978a7baa951f.jpg
708 ms
p_660a96e911237_e9157c471f4cb.jpg
673 ms
p_660172f0c9961_2ac396f3cefb5.jpg
675 ms
p_65fed14e479d7_49bbf886edf9a.jpg
678 ms
p_6579ca430520b_208958f70298d.jpg
707 ms
p_6574daf44b342_8810fb888866f.jpg
715 ms
p_654bb07c31ebe_d01b7aa3c6299.png
712 ms
p_5c891b62a62b5_392938bd77b0c.jpg
673 ms
p_5c891bd02a8f8_75c1cab2fd69b.jpg
679 ms
p_5c8a2da2a7f6b_23adf15b13737.jpg
678 ms
p_5c8a2db6b4f0b_85cc304392390.jpg
707 ms
f-effect.png
714 ms
f-effect-icon.png
719 ms
news.png
672 ms
footer_android.jpg
679 ms
footer_ios.jpg
674 ms
ios_helper.png
705 ms
payment_logos.png
715 ms
skin.css
560 ms
dark-bottom.css
49 ms
fratelli.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fratelli.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
fratelli.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Fratelli.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 Fratelli.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.
fratelli.bg
Open Graph description is not detected on the main page of Fratelli. 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: