1.3 sec in total
140 ms
1.1 sec
115 ms
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.comWe analyzed Famelia.com page load time and found that the first response time was 140 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
famelia.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value7.1 s
6/100
25%
Value9.2 s
13/100
10%
Value3,800 ms
1/100
30%
Value0
100/100
15%
Value21.4 s
1/100
10%
140 ms
80 ms
84 ms
66 ms
105 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Famelia.com, 75% (30 requests) were made to Static.parastorage.com and 13% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (659 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.1 MB (77%)
2.8 MB
650.9 kB
In fact, the total size of Famelia.com main page is 2.8 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. 70% of websites need less resources to load. Javascripts take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 19.9 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 19.9 kB or 76% of the original size.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 5.8 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. Famelia.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.
Number of requests can be reduced by 29 (76%)
38
9
The browser has sent 38 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 30 to 1 for JavaScripts and as a result speed up the page load time.
famelia.com
140 ms
www.famelia.com
80 ms
bt
84 ms
require.min.js
66 ms
main-r.min.js
105 ms
viewer.css
69 ms
UpgradeBrowser.js
81 ms
ugc-viewer
56 ms
dynamicmodel
54 ms
ef27d8_41c99fc33a50eb68865c0c6e4809422b_543.json.z
659 ms
bt
123 ms
skins.min.js
287 ms
components.min.js
118 ms
utils.min.js
123 ms
core.min.js
63 ms
react-with-addons.min.js
122 ms
lodash.min.js
117 ms
TweenMax.min.js
286 ms
layout.min.js
281 ms
tpa.min.js
279 ms
fonts.min.js
280 ms
animations.min.js
280 ms
swfobject.min.js
280 ms
mousetrap.min.js
464 ms
tweenEngine.min.js
465 ms
DrawSVGPlugin.min.js
280 ms
react-dom.min.js
467 ms
ScrollToPlugin.min.js
280 ms
widgets.min.js
458 ms
experiment.js
458 ms
render.min.js
458 ms
wixappsCore.min.js
465 ms
wixappsClassics.min.js
463 ms
wixappsBuilder.min.js
451 ms
zepto.min.js
451 ms
color.min.js
452 ms
react-dom-server.min.js
325 ms
bt
155 ms
bt
37 ms
dc.js
32 ms
famelia.com accessibility score
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
Links do not have a discernible name
famelia.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
famelia.com SEO score
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
Tap targets are not sized appropriately
EN
N/A
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 neither this language nor any other was claimed in <html> or <meta> tags. 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.
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: