Tools & Wizards About Us
imperialflowerslexington.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

imperialflowerslexington.com

Imperial Flowers - Lexington KY Florist - Flower Delivery Lexington - Lexington Florist KY

Page Load Speed

4 sec in total

First Response

376 ms

Resources Loaded

2.9 sec

Page Rendered

783 ms

imperialflowerslexington.com screenshot

About Website

Click here to check amazing Imperial Flowers Lexington content. Otherwise, check out these important facts you probably never knew about imperialflowerslexington.com

Imperial Flowers is a local Lexington, Kentucky florist with over 35 years of professional floral design experience. Call 859-233-7486 or 800-888-7486.

Visit imperialflowerslexington.com

Key Findings

We analyzed Imperialflowerslexington.com page load time and found that the first response time was 376 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

imperialflowerslexington.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.878

3/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

www.imperialflowerslexington.com

376 ms

common.css

116 ms

layout.css

177 ms

input.css

182 ms

product.css

179 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 91% of them (106 requests) were addressed to the original Imperialflowerslexington.com, 3% (4 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Rw1.marchex.io. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Imperialflowerslexington.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (28%)

Content Size

5.8 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imperialflowerslexington.com main page is 5.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. 40% of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 84.0 kB

  • Original 97.6 kB
  • After minification 97.2 kB
  • After compression 13.5 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 84.0 kB or 86% of the original size.

Image Optimization

-27%

Potential reduce by 1.5 MB

  • Original 5.5 MB
  • After minification 4.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. Obviously, Imperial Flowers Lexington needs image optimization as it can save up to 1.5 MB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 48.2 kB

  • Original 114.1 kB
  • After minification 103.9 kB
  • After compression 65.9 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 48.2 kB or 42% of the original size.

CSS Optimization

-69%

Potential reduce by 28.3 kB

  • Original 41.0 kB
  • After minification 37.0 kB
  • After compression 12.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. Imperialflowerslexington.com needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (45%)

Requests Now

116

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.imperialflowerslexington.com

www.imperialflowerslexington.com

376 ms

common.css

common.css

116 ms

layout.css

layout.css

177 ms

input.css

input.css

182 ms

product.css

product.css

179 ms

site.css

site.css

180 ms

pageelements.css

pageelements.css

178 ms

preview.css

preview.css

180 ms

prototype.js

prototype.js

312 ms

effects.js

effects.js

298 ms

server.js

server.js

240 ms

bounds.js

bounds.js

297 ms

tip.js

tip.js

239 ms

touch.js

touch.js

240 ms

site.js

site.js

299 ms

stats.js

stats.js

299 ms

form.js

form.js

301 ms

productprice.js

productprice.js

357 ms

table.js

table.js

358 ms

action.js

action.js

360 ms

number-changer.js

number-changer.js

45 ms

top_radius.png

top_radius.png

72 ms

site_radius.png

site_radius.png

72 ms

logo.img

logo.img

179 ms

bottom_radius.png

bottom_radius.png

70 ms

pagetitle.img

pagetitle.img

70 ms

corner.img

corner.img

71 ms

tabitem.img

tabitem.img

130 ms

tabitem.img

tabitem.img

131 ms

tabitem.img

tabitem.img

132 ms

tabitem.img

tabitem.img

129 ms

tabitem.img

tabitem.img

132 ms

tabitem.img

tabitem.img

190 ms

tabitem.img

tabitem.img

190 ms

tabitem.img

tabitem.img

191 ms

tabitem.img

tabitem.img

192 ms

tabitem.img

tabitem.img

193 ms

tabitem.img

tabitem.img

239 ms

tabitem.img

tabitem.img

250 ms

tabitem.img

tabitem.img

255 ms

tabitem.img

tabitem.img

256 ms

tabitem.img

tabitem.img

256 ms

tabitem.img

tabitem.img

254 ms

tabitem.img

tabitem.img

299 ms

tabitem.img

tabitem.img

309 ms

tabitem.img

tabitem.img

315 ms

tabitem.img

tabitem.img

314 ms

tabitem.img

tabitem.img

316 ms

tabitem.img

tabitem.img

316 ms

tabitem.img

tabitem.img

370 ms

tabitem.img

tabitem.img

374 ms

tabitem.img

tabitem.img

375 ms

heading.img

heading.img

376 ms

thumbnail.img

thumbnail.img

434 ms

DreamingOfBlue.jpg

DreamingOfBlue.jpg

498 ms

heading.img

heading.img

420 ms

thumbnail.img

thumbnail.img

421 ms

sdk.js

sdk.js

46 ms

widgets.js

widgets.js

131 ms

getnumdata.js

getnumdata.js

57 ms

thumbnail.img

thumbnail.img

371 ms

thumbnail.img

thumbnail.img

372 ms

thumbnail.img

thumbnail.img

417 ms

thumbnail.img

thumbnail.img

432 ms

thumbnail.img

thumbnail.img

430 ms

sdk.js

sdk.js

5 ms

44 ms

thumbnail.img

thumbnail.img

380 ms

thumbnail.img

thumbnail.img

379 ms

thumbnail.img

thumbnail.img

419 ms

thumbnail.img

thumbnail.img

428 ms

thumbnail.img

thumbnail.img

430 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

58 ms

thumbnail.img

thumbnail.img

383 ms

thumbnail.img

thumbnail.img

377 ms

thumbnail.img

thumbnail.img

374 ms

thumbnail.img

thumbnail.img

420 ms

thumbnail.img

thumbnail.img

428 ms

thumbnail.img

thumbnail.img

428 ms

settings

settings

77 ms

image.img

image.img

732 ms

image.img

image.img

956 ms

image.img

image.img

781 ms

image.img

image.img

765 ms

image.img

image.img

837 ms

image.img

image.img

774 ms

image.img

image.img

1196 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

image.img

image.img

888 ms

image.img

image.img

1069 ms

image.img

image.img

1246 ms

image.img

image.img

954 ms

image.img

image.img

1291 ms

embeds

embeds

22 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

33 ms

heading.img

heading.img

894 ms

heading.img

heading.img

952 ms

thumbnail.img

thumbnail.img

957 ms

thumbnail.img

thumbnail.img

1013 ms

thumbnail.img

thumbnail.img

975 ms

thumbnail.img

thumbnail.img

1012 ms

thumbnail.img

thumbnail.img

1016 ms

thumbnail.img

thumbnail.img

1021 ms

thumbnail.img

thumbnail.img

1069 ms

thumbnail.img

thumbnail.img

1029 ms

thumbnail.img

thumbnail.img

1022 ms

thumbnail.img

thumbnail.img

1057 ms

thumbnail.img

thumbnail.img

1066 ms

thumbnail.img

thumbnail.img

1068 ms

thumbnail.img

thumbnail.img

1078 ms

corner.img

corner.img

1070 ms

image.img

image.img

1069 ms

image.img

image.img

1074 ms

web_hosting_companies.png

web_hosting_companies.png

1075 ms

1706017013283

1706017013283

1081 ms

siteimage.img

siteimage.img

1162 ms

gradient.png

gradient.png

1068 ms

Accessibility Review

imperialflowerslexington.com accessibility score

62

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

imperialflowerslexington.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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

imperialflowerslexington.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imperialflowerslexington.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 Imperialflowerslexington.com main page’s claimed encoding is iso8859-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

imperialflowerslexington.com

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