Tools & Wizards About Us
olanderflorist.com screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

olanderflorist.com

Olander Florist :: Send Flowers Plants Roses Funeral Online Chicago

Page Load Speed

2.5 sec in total

First Response

141 ms

Resources Loaded

2 sec

Page Rendered

361 ms

olanderflorist.com screenshot

About Website

Click here to check amazing Olander Florist content. Otherwise, check out these important facts you probably never knew about olanderflorist.com

A REAL FLORIST providing daily delivery to Harvey, IL, throughout Chicago and the south suburbs, and featuring an incomparable choice for floral arrangements & gifts at our floral shops in the Chicago...

Visit olanderflorist.com

Key Findings

We analyzed Olanderflorist.com page load time and found that the first response time was 141 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

olanderflorist.com performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.249

50/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

olanderflorist.com

141 ms

olanderflorist.com

1605 ms

INVOICE.css

115 ms

maincss.css

143 ms

menu187id47_style.css

170 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 94% of them (30 requests) were addressed to the original Olanderflorist.com, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Media99.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Olanderflorist.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.4 kB (6%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Olanderflorist.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. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 19.1 kB

  • Original 23.1 kB
  • After minification 18.9 kB
  • After compression 4.0 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 4.2 kB, which is 18% 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 19.1 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 13.5 kB

  • Original 1.2 MB
  • After minification 1.2 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. Olander Florist images are well optimized though.

CSS Optimization

-83%

Potential reduce by 38.8 kB

  • Original 46.9 kB
  • After minification 35.8 kB
  • After compression 8.1 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. Olanderflorist.com needs all CSS files to be minified and compressed as it can save up to 38.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (17%)

Requests Now

30

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olander 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

olanderflorist.com

olanderflorist.com

141 ms

olanderflorist.com

olanderflorist.com

1605 ms

INVOICE.css

INVOICE.css

115 ms

maincss.css

maincss.css

143 ms

menu187id47_style.css

menu187id47_style.css

170 ms

js

js

77 ms

header-background.jpg

header-background.jpg

102 ms

olander-logo.png

olander-logo.png

39 ms

Thanksgiving24-1.jpg

Thanksgiving24-1.jpg

135 ms

FCSF-14xg.jpg

FCSF-14xg.jpg

108 ms

more-info.png

more-info.png

100 ms

FCWB-01xg.jpg

FCWB-01xg.jpg

43 ms

FCSF-05xg.jpg

FCSF-05xg.jpg

70 ms

FCROSF-01xg.jpg

FCROSF-01xg.jpg

69 ms

FCYL-04xg.jpg

FCYL-04xg.jpg

37 ms

FCB-57_Designers_Choice_Thanksgiving_Centerpiece_1x1xg.jpg

FCB-57_Designers_Choice_Thanksgiving_Centerpiece_1x1xg.jpg

36 ms

FCRS-20xg.jpg

FCRS-20xg.jpg

36 ms

FCBD-01xg.jpg

FCBD-01xg.jpg

36 ms

FCPL-22xg.jpg

FCPL-22xg.jpg

36 ms

FCP-71xg.jpg

FCP-71xg.jpg

35 ms

FCPH-31xg.jpg

FCPH-31xg.jpg

36 ms

FCB-70xg.jpg

FCB-70xg.jpg

36 ms

m99-logosm.jpg

m99-logosm.jpg

171 ms

footer-background-graphic.jpg

footer-background-graphic.jpg

109 ms

facebook.png

facebook.png

41 ms

Instagram.png

Instagram.png

41 ms

Pinterest.png

Pinterest.png

40 ms

schultzflorists_logo_small.png

schultzflorists_logo_small.png

73 ms

bee.png

bee.png

74 ms

INVOICE-mobile.css

INVOICE-mobile.css

37 ms

tabletcss.css

tabletcss.css

38 ms

mobilecss.css

mobilecss.css

37 ms

Accessibility Review

olanderflorist.com accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

olanderflorist.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

olanderflorist.com SEO score

98

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Olanderflorist.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 Olanderflorist.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

olanderflorist.com

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