Tools & Wizards About Us
famelia.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

famelia.com

Italian Cuisine in Toronto | F'Amelia Ristorante | Ontario

Page Load Speed

3.8 sec in total

First Response

631 ms

Resources Loaded

3.1 sec

Page Rendered

55 ms

famelia.com screenshot

About Website

Visit famelia.com now to see the best up-to-date F Amelia content and also check out these interesting facts you probably never knew about famelia.com

Nestled in the heart of Cabbagetown, tucked away on Amelia Street, F'Amelia Ristorante delivers authentic northern Italian cuisine. Treat yourself to fresh made pasta & pizzas or our amazing and daily...

Visit famelia.com

Key Findings

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

Performance Metrics

famelia.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value3,350 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

www.famelia.com

631 ms

minified.js

35 ms

focus-within-polyfill.js

32 ms

polyfill.min.js

876 ms

thunderbolt-commons.1fbb1c52.bundle.min.js

61 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Famelia.com, 33% (13 requests) were made to Static.parastorage.com and 31% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (876 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 884.0 kB (67%)

Content Size

1.3 MB

After Optimization

437.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Famelia.com main page is 1.3 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. 30% of websites need less resources to load. HTML takes 819.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 658.0 kB

  • Original 819.1 kB
  • After minification 817.6 kB
  • After compression 161.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 658.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 29.6 kB
  • After minification 29.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. F Amelia images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 225.9 kB

  • Original 472.9 kB
  • After minification 472.9 kB
  • After compression 246.9 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 225.9 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (42%)

Requests Now

26

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F Amelia. 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.

Network Requests Diagram

www.famelia.com

www.famelia.com

631 ms

minified.js

minified.js

35 ms

focus-within-polyfill.js

focus-within-polyfill.js

32 ms

polyfill.min.js

polyfill.min.js

876 ms

thunderbolt-commons.1fbb1c52.bundle.min.js

thunderbolt-commons.1fbb1c52.bundle.min.js

61 ms

main.80be598a.bundle.min.js

main.80be598a.bundle.min.js

62 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

24 ms

lodash.min.js

lodash.min.js

61 ms

react.production.min.js

react.production.min.js

60 ms

react-dom.production.min.js

react-dom.production.min.js

62 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

62 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

62 ms

f'amelia.jpg

f'amelia.jpg

332 ms

Atrium.jpg

Atrium.jpg

540 ms

Bar.jpg

Bar.jpg

521 ms

Hard%20at%20Work!.jpg

Hard%20at%20Work!.jpg

559 ms

ef27d8_73a1600064604d508140c44fc50f4265~mv2.jpg

ef27d8_73a1600064604d508140c44fc50f4265~mv2.jpg

614 ms

20221201_183138.jpg

20221201_183138.jpg

600 ms

20240423_200542.jpg

20240423_200542.jpg

518 ms

Mmmm%20Zaaaa!%20%23FAmelia%20%23cabbagetown%20%23woodf.jpg

Mmmm%20Zaaaa!%20%23FAmelia%20%23cabbagetown%20%23woodf.jpg

797 ms

ef27d8_2bd23205b17143b9accc61db4de4845a~mv2.jpg

ef27d8_2bd23205b17143b9accc61db4de4845a~mv2.jpg

846 ms

Coming%20soon!!%20%23FAmelia%20is%20opening%20up%20for.jpg

Coming%20soon!!%20%23FAmelia%20is%20opening%20up%20for.jpg

848 ms

bundle.min.js

bundle.min.js

76 ms

105 ms

98 ms

101 ms

100 ms

98 ms

94 ms

136 ms

133 ms

131 ms

128 ms

127 ms

129 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

16 ms

deprecation-style.v5.css

deprecation-style.v5.css

7 ms

right-arrow.svg

right-arrow.svg

6 ms

Accessibility Review

famelia.com accessibility score

100

Accessibility Issues

Best Practices

famelia.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

famelia.com SEO score

99

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

famelia.com

Open Graph data is detected on the main page of F Amelia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: