Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

hapni.bg

Takeaway.com | Поръчай храна онлайн от любимите ти ресторанти

Page Load Speed

8.2 sec in total

First Response

579 ms

Resources Loaded

7.2 sec

Page Rendered

386 ms

hapni.bg screenshot

About Website

Click here to check amazing Hapni content. Otherwise, check out these important facts you probably never knew about hapni.bg

Поръчай храна онлайн с Takeaway.com - най-голямата платформа за поръчка на храна в България. 1000+ партньорски ресторанта с огромен избор от кухни. Какво ти се хапва днес?

Visit hapni.bg

Key Findings

We analyzed Hapni.bg page load time and found that the first response time was 579 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

hapni.bg performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

29/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value6,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

hapni.bg

579 ms

hapni.foodpanda.bg

3545 ms

shopMain-039908fec9bf5dd298df55bae1571541.css

14 ms

shopHead-cbee47b2a27a292b713accac34ab977a.js

47 ms

566322169.js

58 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Hapni.bg, 31% (10 requests) were made to Marketing.foodpanda.my and 22% (7 requests) were made to Marketing.foodpanda.bg. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Hapni.foodpanda.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 728.9 kB (34%)

Content Size

2.2 MB

After Optimization

1.4 MB

In fact, the total size of Hapni.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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 295 B

  • Original 574 B
  • After minification 526 B
  • After compression 279 B

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 295 B or 51% of the original size.

Image Optimization

-4%

Potential reduce by 54.9 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. Hapni images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 404.1 kB

  • Original 602.6 kB
  • After minification 602.6 kB
  • After compression 198.6 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 404.1 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 269.6 kB

  • Original 314.2 kB
  • After minification 313.9 kB
  • After compression 44.6 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. Hapni.bg needs all CSS files to be minified and compressed as it can save up to 269.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (16%)

Requests Now

31

After Optimization

26

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hapni. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

hapni.bg accessibility score

100

Accessibility Issues

Best Practices

hapni.bg best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

hapni.bg SEO score

92

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hapni.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hapni.bg main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Hapni. 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: