Tools & Wizards About Us
eazyfnb.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

eazyfnb.com

Contactless Menu, Touchless & Digital Menu for Restaurants

Page Load Speed

3.1 sec in total

First Response

371 ms

Resources Loaded

1.8 sec

Page Rendered

889 ms

eazyfnb.com screenshot

About Website

Welcome to eazyfnb.com homepage info - get ready to check Eazyfnb best content right away, or after learning these important things about eazyfnb.com

Get amazing contactless menu for your restaurants in 2 hours, our touchless menu have amazing design digital menu that have menu, call waiter, wifi & reviews

Visit eazyfnb.com

Key Findings

We analyzed Eazyfnb.com page load time and found that the first response time was 371 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

eazyfnb.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

eazyfnb.com

371 ms

app.css

16 ms

js

113 ms

email-decode.min.js

41 ms

2dd2543b10.js

99 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 86% of them (76 requests) were addressed to the original Eazyfnb.com, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Static.getbutton.io. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Eazyfnb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 965.7 kB (10%)

Content Size

9.7 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eazyfnb.com main page is 9.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 43.9 kB

  • Original 51.5 kB
  • After minification 31.6 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 19.9 kB, which is 39% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.9 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 918.9 kB

  • Original 9.0 MB
  • After minification 8.1 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. Eazyfnb images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 73 B

  • Original 609.8 kB
  • After minification 609.8 kB
  • After compression 609.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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 2.9 kB

  • Original 30.9 kB
  • After minification 30.9 kB
  • After compression 28.1 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. Eazyfnb.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (12%)

Requests Now

86

After Optimization

76

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eazyfnb.com

eazyfnb.com

371 ms

app.css

app.css

16 ms

js

js

113 ms

email-decode.min.js

email-decode.min.js

41 ms

2dd2543b10.js

2dd2543b10.js

99 ms

app.js

app.js

67 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

122 ms

init.js

init.js

173 ms

fbevents.js

fbevents.js

47 ms

hotjar-1839202.js

hotjar-1839202.js

134 ms

facebook.svg

facebook.svg

1244 ms

instagram.svg

instagram.svg

291 ms

linkedin.svg

linkedin.svg

575 ms

youtube.svg

youtube.svg

296 ms

header.jpg

header.jpg

80 ms

logo.svg

logo.svg

81 ms

mobile-logo.svg

mobile-logo.svg

96 ms

logobg.png

logobg.png

96 ms

1586152463.png

1586152463.png

119 ms

1590996945.png

1590996945.png

119 ms

1576658502.png

1576658502.png

120 ms

1596039534.JPG

1596039534.JPG

122 ms

1590925119.png

1590925119.png

121 ms

1590993273.png

1590993273.png

123 ms

1590909518.png

1590909518.png

122 ms

1591000484.png

1591000484.png

124 ms

1578467798.png

1578467798.png

124 ms

1592720757.png

1592720757.png

144 ms

1596709414.png

1596709414.png

145 ms

1589010116.png

1589010116.png

145 ms

1679033499.jpg

1679033499.jpg

146 ms

1592286047.png

1592286047.png

147 ms

1708332781.png

1708332781.png

230 ms

1594213174.png

1594213174.png

232 ms

1594530436.png

1594530436.png

233 ms

1594897170.png

1594897170.png

233 ms

1595331649.png

1595331649.png

235 ms

1597902580.png

1597902580.png

236 ms

1633760812.png

1633760812.png

235 ms

1645367292.jpeg

1645367292.jpeg

236 ms

1603795535.png

1603795535.png

237 ms

1604315517.png

1604315517.png

238 ms

1604316322.png

1604316322.png

239 ms

1606217080.png

1606217080.png

238 ms

1606052557.png

1606052557.png

286 ms

1607523271.png

1607523271.png

254 ms

1607579819.png

1607579819.png

202 ms

1607589730.png

1607589730.png

197 ms

1607776142.png

1607776142.png

467 ms

1608967796.png

1608967796.png

177 ms

1609162323.png

1609162323.png

175 ms

1610439047.png

1610439047.png

184 ms

1614500146.png

1614500146.png

184 ms

1617256546.png

1617256546.png

449 ms

1620541746.png

1620541746.png

195 ms

1622020559.png

1622020559.png

193 ms

1622524134.png

1622524134.png

207 ms

1627798873.png

1627798873.png

203 ms

js

js

99 ms

analytics.js

analytics.js

23 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

89 ms

1629967795.png

1629967795.png

193 ms

1632902075.png

1632902075.png

200 ms

1636355234.svg

1636355234.svg

202 ms

1650611075.png

1650611075.png

244 ms

1669809533.png

1669809533.png

218 ms

1683230417.png

1683230417.png

228 ms

bundle.js

bundle.js

71 ms

collect

collect

56 ms

1685014096.png

1685014096.png

156 ms

1701083889.png

1701083889.png

167 ms

1708333990.png

1708333990.png

168 ms

phone.png

phone.png

176 ms

mobile-1.png

mobile-1.png

180 ms

tablet.png

tablet.png

196 ms

mobile-2.png

mobile-2.png

197 ms

bg02.jpg

bg02.jpg

210 ms

play-store.svg

play-store.svg

206 ms

signup.svg

signup.svg

221 ms

add-logo.svg

add-logo.svg

218 ms

choose-design.svg

choose-design.svg

182 ms

collect

collect

27 ms

menu.svg

menu.svg

187 ms

lower-bg.png

lower-bg.png

1106 ms

tablet2.png

tablet2.png

198 ms

14.png

14.png

213 ms

15.png

15.png

233 ms

11.png

11.png

279 ms

Accessibility Review

eazyfnb.com accessibility score

80

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

eazyfnb.com 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

eazyfnb.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eazyfnb.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eazyfnb.com 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

eazyfnb.com

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