Access 416-florist.com. Toronto Florist & Flower Shop, Your Source For Flowers and Baskets

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.418

23/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

416-florist.com

48 ms

416-florist.com

97 ms

www.416-florist.com

724 ms

gtm.js

76 ms

bootstrap.css

65 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 69% of them (53 requests) were addressed to the original 416-florist.com, 8% (6 requests) were made to Google.com and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (724 ms) belongs to the original domain 416-florist.com.

Content Size

2.8 MB

After Optimization

2.5 MB

In fact, the total size of 416-florist.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. 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 60.2 kB

Original 77.6 kB
After minification 60.0 kB
After compression 17.4 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 17.6 kB, which is 23% 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 60.2 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 104.5 kB

Original 2.1 MB
After minification 2.0 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. 416 Florist images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 70.3 kB

Original 494.3 kB
After minification 494.0 kB
After compression 424.0 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 70.3 kB or 14% of the original size.

CSS Optimization

-9%

Potential reduce by 8.3 kB

Original 91.5 kB
After minification 91.5 kB
After compression 83.2 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. 416-florist.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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/).

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 416-florist.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 416-florist.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

416-florist.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Toronto Florist & Flower Shop, Your Source For Flowers and Baskets | 416-florist

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

416-florist.com

416-florist.com

www.416-florist.com

gtm.js

bootstrap.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

416-florist.com

416-florist.com

www.416-florist.com

gtm.js

bootstrap.css

bootstrap-theme.css

cssmenu.css

public.css

style.css

print.min.css

owl.carousel.css

owl.theme.css

masterslider.css

masterslider.main.css

ms-slider.css

font-moon.css

icon-empty.css

bootstrap-stars.css

jquery-ui.css

api.js

jquery.min(2.1.3).js

jquery-ui.js

bootstrap.js

owl.carousel.js

jquery.barrating.min.js

jRating.jquery.js

notify.js

jquery.mask.js

jquery.validate.js

cssmenu.js

app.1.js

public.1.js

account.1.js

checkout.1.js

cart.1.js

print.js

conversion.js

analytics.js

destination

collect

js

recaptcha__en.js

cot.js