7.6 sec in total
2 sec
5.1 sec
441 ms
Welcome to fancy.bg homepage info - get ready to check FANCY best content for Bulgaria right away, or after learning these important things about fancy.bg
Ресторант “FANCY“ отваря отново врати за вас с изцяло обновен интериор, страхотна отопляема зимна градина и съвсем ново меню.
Visit fancy.bgWe analyzed Fancy.bg page load time and found that the first response time was 2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fancy.bg performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value17.8 s
0/100
25%
Value10.3 s
8/100
10%
Value740 ms
40/100
30%
Value0.103
89/100
15%
Value16.7 s
5/100
10%
2027 ms
863 ms
1032 ms
721 ms
1547 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 95% of them (55 requests) were addressed to the original Fancy.bg, 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Fancy.bg.
Page size can be reduced by 485.0 kB (45%)
1.1 MB
602.6 kB
In fact, the total size of Fancy.bg main page is 1.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. 40% of websites need less resources to load. Images take 629.6 kB which makes up the majority of the site volume.
Potential reduce by 24.1 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 24.1 kB or 79% of the original size.
Potential reduce by 140.3 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. Obviously, FANCY needs image optimization as it can save up to 140.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 264.3 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 264.3 kB or 73% of the original size.
Potential reduce by 56.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. Fancy.bg needs all CSS files to be minified and compressed as it can save up to 56.2 kB or 86% of the original size.
Number of requests can be reduced by 19 (36%)
53
34
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FANCY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
fancy.bg
2027 ms
styles.css
863 ms
jquery.min.js
1032 ms
jquery-ui.css
721 ms
jquery-ui.min.js
1547 ms
ui.selectmenu.js
754 ms
fncins.js
497 ms
jquery.flow.1.1.min.js
664 ms
fade.js
838 ms
swfobject.js
1088 ms
jquery.simplemodal.js
1105 ms
init.js
1004 ms
wz_tooltip.js
1245 ms
jcart-javascript.php
1095 ms
bgr.gif
319 ms
ga.js
36 ms
spinner.gif
182 ms
ajax-loader.gif
182 ms
capa.jpg
608 ms
.png
187 ms
FANCY_PARK_100x75.jpg
199 ms
newsFANCYTG.jpg
381 ms
NEWSftg.jpg
507 ms
newsINDONESIA2.jpg
550 ms
newsFRENCH.jpg
532 ms
newsINDONESIA.jpg
530 ms
NEWSPORTUGAL.jpg
539 ms
NorthAfricaNews.jpg
838 ms
newsNEWMENU2.jpg
829 ms
MALEVtumb.jpg
832 ms
newsHUNGARIAN.jpg
697 ms
newsITALY.jpg
865 ms
newsAMERICANl.jpg
764 ms
NEWScoffeeacademia.jpg
854 ms
newmenu2.jpg
915 ms
bulgarian.jpg
975 ms
frenchcuisine1.jpg
1132 ms
cbgr.png
986 ms
htbg.gif
1004 ms
logo.gif
1017 ms
flag_bg.gif
1058 ms
flag_en.gif
1118 ms
tmb.gif
1152 ms
lbbg.gif
1164 ms
tmlbg.gif
1179 ms
ul1_bg.gif
1209 ms
smmap.gif
1267 ms
__utm.gif
71 ms
ejlf.gif
1214 ms
ejrg.gif
1264 ms
fbgr.png
1442 ms
flog.gif
1300 ms
fbutt.gif
1358 ms
__utm.gif
5 ms
ui-bg_glass_20_555555_1x400c.png
1275 ms
ui-icons_cccccc_256x240.png
1487 ms
ui-bg_inset-soft_25_000000_1x100b.png
1324 ms
print.css
175 ms
fancy.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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fancy.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
fancy.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
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fancy.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 Fancy.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.
fancy.bg
Open Graph description is not detected on the main page of FANCY. 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: