5.2 sec in total
225 ms
3.9 sec
1 sec
Visit phofirenze.com now to see the best up-to-date PHO Firenze content for Italy and also check out these interesting facts you probably never knew about phofirenze.com
Benvenuta nel sito ufficiale di PHO Firenze! Scopri le nuove collezioni per la stagione Fall Winter 20/21: abiti donna, gonne, top, accessori e molto altro.
Visit phofirenze.comWe analyzed Phofirenze.com page load time and found that the first response time was 225 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
phofirenze.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value6.3 s
10/100
25%
Value10.1 s
9/100
10%
Value220 ms
88/100
30%
Value0.035
100/100
15%
Value13.0 s
13/100
10%
225 ms
394 ms
536 ms
99 ms
196 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 94% of them (118 requests) were addressed to the original Phofirenze.com, 2% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Phofirenze.com.
Page size can be reduced by 297.4 kB (10%)
3.1 MB
2.8 MB
In fact, the total size of Phofirenze.com main page is 3.1 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.2 MB which makes up the majority of the site volume.
Potential reduce by 86.3 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 86.3 kB or 79% of the original size.
Potential reduce by 106.8 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. PHO Firenze images are well optimized though.
Potential reduce by 77.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 77.6 kB or 13% of the original size.
Potential reduce by 26.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. Phofirenze.com needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 21% of the original size.
Number of requests can be reduced by 107 (91%)
118
11
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PHO Firenze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 71 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
phofirenze.com
225 ms
phofirenze.com
394 ms
www.phofirenze.com
536 ms
front-css.css
99 ms
new-flags.css
196 ms
js_composer.min.css
446 ms
bootstrap-light.min.css
285 ms
base.min.css
291 ms
int-rev-slider.min.css
294 ms
int-wpb-base.min.css
297 ms
int-wpb-base-deprecated.min.css
298 ms
woo-opt-sticky-notices.min.css
380 ms
woocommerce-base.min.css
388 ms
mod-star-rating.min.css
389 ms
woo-el-track-order.min.css
394 ms
woo-mod-block-notices.min.css
395 ms
woo-mod-shop-attributes.min.css
473 ms
opt-carousel-disable.min.css
483 ms
header-base.min.css
486 ms
mod-tools.min.css
490 ms
header-el-base.min.css
491 ms
el-social-icons.min.css
532 ms
header-el-search.min.css
567 ms
header-el-mobile-nav-dropdown.min.css
579 ms
el-section-title.min.css
582 ms
el-section-title-style-simple-and-brd.min.css
585 ms
mod-highlighted-text.min.css
588 ms
project-alt.min.css
619 ms
lib-photoswipe.min.css
660 ms
portfolio-base.min.css
674 ms
footer-base.min.css
679 ms
opt-scrolltotop.min.css
681 ms
wd-search-results.min.css
684 ms
wd-search-form.min.css
707 ms
opt-cookies.min.css
754 ms
header-el-search-fullscreen-general.min.css
770 ms
header-el-search-fullscreen-1.min.css
775 ms
xts-theme_settings_default-1707470772.css
776 ms
css
38 ms
platform.js
27 ms
css
56 ms
rs6.css
876 ms
platform.js
35 ms
jquery.min.js
704 ms
jquery-migrate.min.js
657 ms
jquery.blockUI.min.js
589 ms
add-to-cart.min.js
588 ms
js.cookie.min.js
585 ms
woocommerce.min.js
595 ms
woocommerce-add-to-cart.js
652 ms
front-js.js
591 ms
device.min.js
588 ms
scrollBar.min.js
589 ms
updateCartFragmentsFix.js
593 ms
rbtools.min.js
746 ms
rs6.min.js
870 ms
sourcebuster.min.js
668 ms
order-attribution.min.js
658 ms
react.min.js
654 ms
react-jsx-runtime.min.js
651 ms
hooks.min.js
714 ms
deprecated.min.js
674 ms
dom.min.js
636 ms
react-dom.min.js
723 ms
escape-html.min.js
621 ms
element.min.js
703 ms
is-shallow-equal.min.js
711 ms
i18n.min.js
681 ms
keycodes.min.js
640 ms
priority-queue.min.js
701 ms
compose.min.js
717 ms
private-apis.min.js
716 ms
redux-routine.min.js
712 ms
data.min.js
692 ms
lodash.min.js
675 ms
wp-polyfill.min.js
694 ms
wc-blocks-registry.js
715 ms
url.min.js
710 ms
api-fetch.min.js
687 ms
wc-settings.js
645 ms
data-controls.min.js
657 ms
html-entities.min.js
680 ms
notices.min.js
713 ms
wc-blocks-middleware.js
710 ms
wc-blocks-data.js
803 ms
dom-ready.min.js
650 ms
a11y.min.js
655 ms
primitives.min.js
671 ms
phodirenze-logo-dark.svg
157 ms
warning.min.js
705 ms
blocks-components.js
762 ms
e3t5euGtX-Co5MNzeAOqinEYj2rCrdZM.ttf
77 ms
e3tmeuGtX-Co5MNzeAOqinEQfEnS.ttf
114 ms
e3t5euGtX-Co5MNzeAOqinEYo23CrdZM.ttf
137 ms
blocks-checkout.js
559 ms
order-attribution-blocks.min.js
579 ms
js_composer_front.min.js
595 ms
helpers.min.js
646 ms
woocommerceNotices.min.js
668 ms
headerBuilder.min.js
607 ms
menuOffsets.min.js
608 ms
menuSetUp.min.js
619 ms
mobileSearchIcon.min.js
678 ms
imagesloaded.min.js
597 ms
isotope-bundle.min.js
589 ms
masonryLayout.min.js
593 ms
photoswipe-bundle.min.js
606 ms
portfolioPhotoSwipe.min.js
609 ms
callPhotoSwipe.min.js
638 ms
portfolioLoadMore.min.js
603 ms
waypoints.min.js
590 ms
scrollTop.min.js
594 ms
mobileNavigation.min.js
604 ms
autocomplete.min.js
601 ms
ajaxSearch.min.js
637 ms
cookiesPopup.min.js
611 ms
searchFullScreen.min.js
590 ms
pho-firenze-logo-web.svg
676 ms
dummy.png
676 ms
DSC02064-800x1000.jpg
692 ms
R3J09470-800x1000.jpg
839 ms
DSC01790-800x1000.jpg
908 ms
DSC02205-800x1000.jpg
882 ms
Progetto-senza-titolo-45-864x1080.png
1181 ms
image00011-864x1080.jpg
671 ms
phofirenze.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
phofirenze.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
Browser errors were logged to the console
phofirenze.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
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phofirenze.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Italian language. Our system also found out that Phofirenze.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.
phofirenze.com
Open Graph description is not detected on the main page of PHO Firenze. 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: