Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

fancy.bg

Начало - Добре Дошли в нашият подобрен ресторант • FANCY

Page Load Speed

7.6 sec in total

First Response

2 sec

Resources Loaded

5.1 sec

Page Rendered

441 ms

fancy.bg screenshot

About Website

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.bg

Key Findings

We 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.

Performance Metrics

fancy.bg performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value17.8 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.103

89/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

fancy.bg

2027 ms

styles.css

863 ms

jquery.min.js

1032 ms

jquery-ui.css

721 ms

jquery-ui.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 455.9 kB (43%)

Content Size

1.1 MB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 24.1 kB

  • Original 30.4 kB
  • After minification 27.4 kB
  • After compression 6.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 24.1 kB or 79% of the original size.

Image Optimization

-22%

Potential reduce by 140.3 kB

  • Original 629.6 kB
  • After minification 489.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.

JavaScript Optimization

-71%

Potential reduce by 235.2 kB

  • Original 332.9 kB
  • After minification 308.1 kB
  • After compression 97.7 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 235.2 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 56.2 kB

  • Original 65.6 kB
  • After minification 51.4 kB
  • After compression 9.3 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.

Requests Breakdown

Number of requests can be reduced by 19 (36%)

Requests Now

53

After Optimization

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.

Accessibility Review

fancy.bg accessibility score

92

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fancy.bg best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fancy.bg SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    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.

Social Sharing Optimization

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: