2.2 sec in total
106 ms
1.9 sec
244 ms
Welcome to tasteflorence.com homepage info - get ready to check Taste Florence best content right away, or after learning these important things about tasteflorence.com
Join Taste Florence Food and Wine Tours, the first food tour in Florence Italy and still the best. For over 18 years, our team of sommeliers, culinary professors and guides have been serving up fantas...
Visit tasteflorence.comWe analyzed Tasteflorence.com page load time and found that the first response time was 106 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
tasteflorence.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.7 s
31/100
25%
Value10.1 s
9/100
10%
Value3,370 ms
2/100
30%
Value0.012
100/100
15%
Value25.1 s
0/100
10%
106 ms
41 ms
38 ms
1086 ms
68 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tasteflorence.com, 42% (27 requests) were made to Static.wixstatic.com and 18% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 1.6 MB (32%)
4.9 MB
3.4 MB
In fact, the total size of Tasteflorence.com main page is 4.9 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 1.3 MB
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 1.3 MB or 84% of the original size.
Potential reduce by 18 B
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. Taste Florence images are well optimized though.
Potential reduce by 265.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 265.6 kB or 21% of the original size.
Potential reduce by 2.7 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. Tasteflorence.com has all CSS files already compressed.
Number of requests can be reduced by 16 (33%)
49
33
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Taste Florence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
www.tasteflorence.com
106 ms
minified.js
41 ms
focus-within-polyfill.js
38 ms
polyfill.min.js
1086 ms
thunderbolt-commons.1fbb1c52.bundle.min.js
68 ms
main.80be598a.bundle.min.js
67 ms
main.renderer.1d21f023.bundle.min.js
62 ms
lodash.min.js
62 ms
react.production.min.js
60 ms
react-dom.production.min.js
67 ms
siteTags.bundle.min.js
69 ms
wix-perf-measure.umd.min.js
69 ms
94 ms
integration-kit-bundle.js
157 ms
taste-florence-logo-BLACK.png
273 ms
maxresdefault.jpg%202x
35 ms
2ebe21_d1f131a8dbb4404fbb0d49c96ccb2f7b~mv2.jpg
419 ms
2ebe21_7df6ca993a164370a257dd98c8ecbd2e~mv2.jpg
286 ms
2ebe21_f2c1dd42f9844ad498e75b13d8ec65f7~mv2.jpg
287 ms
2ebe21_5d7e817c4b244068a05a68727735cebb~mv2.jpg
286 ms
2ebe21_52ed6afc268242f69783e825736bbb07~mv2.jpg
293 ms
2ebe21_f0f32532fd444d4dbdf87c4a08a70ede~mv2.jpg
286 ms
2ebe21_5285b3c581334da7b172ee6ae6430f31~mv2.jpg
292 ms
2ebe21_6f2c637f1799407dabf4dd78e25f9374~mv2.jpg
288 ms
2ebe21_568935f24db24a15a8fa7770b0a008c8~mv2.jpg
289 ms
2ebe21_d563da8fd3b145718eab9a505566b6eb~mv2.jpg
289 ms
2ebe21_7be1a4110fbd4173bf535a9ce742285a~mv2.jpg
300 ms
2ebe21_bc4ea0f584ba41f9bd1bceb18f58a0d0~mv2.jpg
291 ms
2ebe21_ecc27189933f469a9bce3b7d964a88fa~mv2.jpg
294 ms
2ebe21_993a9e94f1de444b9d56e237ff3017a0~mv2.jpg
295 ms
2ebe21_30d688488bd945f4a202874887dbc06d~mv2.jpg
298 ms
2ebe21_e05d86aa59e04c9985a1028025b617b5~mv2.jpg
297 ms
2ebe21_bb1ffe261a2a409e84ebafc9c30b4bfd~mv2.jpg
298 ms
2ebe21_ffcba794e46c4dc78878591727ff40ee~mv2.jpg
297 ms
2ebe21_4fb64c740f9d432b8a08b6423dfe9c29~mv2.jpg
306 ms
2ebe21_d357e14ced04485da7a476cd5104b347~mv2.jpg
300 ms
2ebe21_29d81089a6104bfcb52b0eb85f4b82b4~mv2.jpg
303 ms
2ebe21_c11a0f1205c94193b9827755669b1f4b~mv2.jpg
301 ms
2ebe21_978347b77677499597cb30d0e2b007fb~mv2.jpg
302 ms
2ebe21_ec8aeb22a04b469a8e98a26679e6f6ee~mv2.jpg
304 ms
2ebe21_2dc106cd18c74f548202843048df0f9b~mv2.jpg
304 ms
2ebe21_c444510a8b924467b279c7f7a2328002~mv2.jpg
304 ms
maxresdefault.jpg
57 ms
bundle.min.js
102 ms
289 ms
bcf54343-d033-41ee-bbd7-2b77df3fe7ba.woff
51 ms
kEF4nGNgYgCDfxMZpjFgAyxAzMjAxMjEXpqXaWTg5AIAYwIEbQA=
50 ms
118 ms
117 ms
109 ms
112 ms
109 ms
109 ms
145 ms
142 ms
142 ms
143 ms
120 ms
109 ms
style-cart.5f09f13d154c8cf1d34a.css
99 ms
fonts.eacdf4961de415ddab83.css
94 ms
output.6bccdc47c4f0.js
96 ms
js
44 ms
djangojs.js
83 ms
output.62baf877751f.js
81 ms
tasteflorence.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
tasteflorence.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
Missing source maps for large first-party JavaScript
tasteflorence.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tasteflorence.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 Tasteflorence.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.
tasteflorence.com
Open Graph data is detected on the main page of Taste Florence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: