Tools & Wizards About Us
cameronpetersfloraldesign.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

cameronpetersfloraldesign.com

Phoenixville PA Florist - FREE Flower Delivery in Phoenixville PA - Cameron Peters Floral Design

Page Load Speed

6.6 sec in total

First Response

2.4 sec

Resources Loaded

3.8 sec

Page Rendered

449 ms

cameronpetersfloraldesign.com screenshot

About Website

Click here to check amazing Cameron Peters Floral Design content. Otherwise, check out these important facts you probably never knew about cameronpetersfloraldesign.com

Cameron Peters Floral Design in Phoenixville, PA, offers FREE SAME-DAY hand delivery for fresh, elegant & affordable arrangements& gift baskets!…

Visit cameronpetersfloraldesign.com

Key Findings

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

Performance Metrics

cameronpetersfloraldesign.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value2,460 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

cameronpetersfloraldesign.com

2378 ms

styles-m.css

49 ms

styles-l.css

72 ms

require.min.js

99 ms

requirejs-min-resolver.min.js

98 ms

Our browser made a total of 160 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cameronpetersfloraldesign.com, 94% (151 requests) were made to Assets.floranext.com and 3% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Cameronpetersfloraldesign.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.4 kB (37%)

Content Size

898.4 kB

After Optimization

565.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cameronpetersfloraldesign.com main page is 898.4 kB. 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. Javascripts take 552.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 160.5 kB

  • Original 195.6 kB
  • After minification 177.3 kB
  • After compression 35.2 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 160.5 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 25.4 kB
  • After minification 25.4 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. Cameron Peters Floral Design images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 172.3 kB

  • Original 552.4 kB
  • After minification 551.8 kB
  • After compression 380.1 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 172.3 kB or 31% of the original size.

CSS Optimization

-0%

Potential reduce by 600 B

  • Original 124.9 kB
  • After minification 124.9 kB
  • After compression 124.3 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. Cameronpetersfloraldesign.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 133 (91%)

Requests Now

146

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cameronpetersfloraldesign.com

cameronpetersfloraldesign.com

2378 ms

styles-m.css

styles-m.css

49 ms

styles-l.css

styles-l.css

72 ms

require.min.js

require.min.js

99 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

98 ms

mixins.min.js

mixins.min.js

104 ms

requirejs-config.min.js

requirejs-config.min.js

98 ms

polyfill.min.js

polyfill.min.js

102 ms

lazysizes.min.js

lazysizes.min.js

102 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

51 ms

common.min.js

common.min.js

52 ms

dataPost.min.js

dataPost.min.js

51 ms

bootstrap.min.js

bootstrap.min.js

49 ms

jquery.min.js

jquery.min.js

52 ms

translate-inline.min.js

translate-inline.min.js

50 ms

mage-translation-dictionary.min.js

mage-translation-dictionary.min.js

50 ms

responsive.min.js

responsive.min.js

133 ms

theme.min.js

theme.min.js

134 ms

opensans-400.woff

opensans-400.woff

125 ms

opensans-300.woff

opensans-300.woff

125 ms

opensans-600.woff

opensans-600.woff

125 ms

opensans-700.woff

opensans-700.woff

124 ms

Poppins-Regular.woff

Poppins-Regular.woff

124 ms

Poppins-Medium.woff

Poppins-Medium.woff

125 ms

Poppins-Light.woff

Poppins-Light.woff

148 ms

Poppins-SemiBold.woff

Poppins-SemiBold.woff

147 ms

embed

embed

337 ms

Review_us_on_GOOGLE_10__63ee7b6d78b7a.png

Review_us_on_GOOGLE_10__63ee7b6d78b7a.png

436 ms

logo-basic-floranext-white.webp

logo-basic-floranext-white.webp

133 ms

Credit_Card_Payment_Accepted_3_.png

Credit_Card_Payment_Accepted_3_.png

433 ms

flowers_1__63ee784762935.png.webp

flowers_1__63ee784762935.png.webp

686 ms

domReady.min.js

domReady.min.js

44 ms

jquery.min.js

jquery.min.js

44 ms

advanced-icons.woff

advanced-icons.woff

42 ms

Blank-Theme-Icons.woff

Blank-Theme-Icons.woff

65 ms

flora-base-icons.woff

flora-base-icons.woff

66 ms

main.min.js

main.min.js

62 ms

bootstrap.min.js

bootstrap.min.js

62 ms

template.min.js

template.min.js

61 ms

confirm.min.js

confirm.min.js

62 ms

widget.min.js

widget.min.js

64 ms

jquery-migrate.min.js

jquery-migrate.min.js

66 ms

translate.min.js

translate.min.js

52 ms

text.min.js

text.min.js

63 ms

tabs.min.js

tabs.min.js

63 ms

smart-keyboard-handler.min.js

smart-keyboard-handler.min.js

74 ms

mage.min.js

mage.min.js

72 ms

ie-class-fixer.min.js

ie-class-fixer.min.js

74 ms

dialog.min.js

dialog.min.js

49 ms

jquery-ui.min.js

jquery-ui.min.js

49 ms

matchMedia.min.js

matchMedia.min.js

50 ms

owl.carousel.min.js

owl.carousel.min.js

39 ms

knockout.min.js

knockout.min.js

32 ms

knockout-es5.min.js

knockout-es5.min.js

39 ms

underscore.min.js

underscore.min.js

26 ms

modal.min.js

modal.min.js

25 ms

core.min.js

core.min.js

61 ms

collapsible.min.js

collapsible.min.js

64 ms

engine.min.js

engine.min.js

60 ms

bootstrap.min.js

bootstrap.min.js

57 ms

bootstrap.min.js

bootstrap.min.js

57 ms

observable_array.min.js

observable_array.min.js

58 ms

bound-nodes.min.js

bound-nodes.min.js

59 ms

scripts.min.js

scripts.min.js

58 ms

button.min.js

button.min.js

56 ms

draggable.min.js

draggable.min.js

71 ms

position.min.js

position.min.js

71 ms

resizable.min.js

resizable.min.js

71 ms

key-codes.min.js

key-codes.min.js

61 ms

.jpg

.jpg

287 ms

knockout-repeat.min.js

knockout-repeat.min.js

30 ms

knockout-fast-foreach.min.js

knockout-fast-foreach.min.js

52 ms

autocomplete.min.js

autocomplete.min.js

80 ms

jquery.storageapi.extended.min.js

jquery.storageapi.extended.min.js

94 ms

wrapper.min.js

wrapper.min.js

125 ms

events.min.js

events.min.js

148 ms

es6-collections.min.js

es6-collections.min.js

164 ms

observable_source.min.js

observable_source.min.js

177 ms

renderer.min.js

renderer.min.js

195 ms

console-logger.min.js

console-logger.min.js

211 ms

resizable.min.js

resizable.min.js

231 ms

i18n.min.js

i18n.min.js

236 ms

scope.min.js

scope.min.js

249 ms

range.min.js

range.min.js

249 ms

mage-init.min.js

mage-init.min.js

270 ms

keyboard.min.js

keyboard.min.js

266 ms

optgroup.min.js

optgroup.min.js

273 ms

after-render.min.js

after-render.min.js

284 ms

autoselect.min.js

autoselect.min.js

284 ms

datepicker.min.js

datepicker.min.js

285 ms

outer_click.min.js

outer_click.min.js

291 ms

fadeVisible.min.js

fadeVisible.min.js

284 ms

collapsible.min.js

collapsible.min.js

286 ms

staticChecked.min.js

staticChecked.min.js

313 ms

simple-checked.min.js

simple-checked.min.js

306 ms

bind-html.min.js

bind-html.min.js

303 ms

tooltip.min.js

tooltip.min.js

301 ms

mouse.min.js

mouse.min.js

305 ms

js

js

31 ms

jquery.cookie.min.js

jquery.cookie.min.js

232 ms

jquery.storageapi.min.js

jquery.storageapi.min.js

247 ms

search.js

search.js

4 ms

geometry.js

geometry.js

7 ms

main.js

main.js

13 ms

class.min.js

class.min.js

161 ms

loader.min.js

loader.min.js

125 ms

local.min.js

local.min.js

117 ms

js-translation.json

js-translation.json

118 ms

logger.min.js

logger.min.js

120 ms

entry-factory.min.js

entry-factory.min.js

134 ms

console-output-handler.min.js

console-output-handler.min.js

137 ms

formatter.min.js

formatter.min.js

130 ms

message-pool.min.js

message-pool.min.js

134 ms

levels-pool.min.js

levels-pool.min.js

129 ms

logger-utils.min.js

logger-utils.min.js

131 ms

async.min.js

async.min.js

148 ms

registry.min.js

registry.min.js

146 ms

slider.min.js

slider.min.js

119 ms

modal-popup.html

modal-popup.html

117 ms

modal-slide.html

modal-slide.html

102 ms

modal-custom.html

modal-custom.html

101 ms

main.min.js

main.min.js

128 ms

calendar.min.js

calendar.min.js

112 ms

moment.min.js

moment.min.js

104 ms

template.min.js

template.min.js

40 ms

entry.min.js

entry.min.js

36 ms

dom-observer.min.js

dom-observer.min.js

34 ms

bindings.min.js

bindings.min.js

28 ms

objects.min.js

objects.min.js

21 ms

strings.min.js

strings.min.js

24 ms

datepicker.min.js

datepicker.min.js

22 ms

timepicker.min.js

timepicker.min.js

30 ms

arrays.min.js

arrays.min.js

28 ms

compare.min.js

compare.min.js

37 ms

misc.min.js

misc.min.js

21 ms

MutationObserver.min.js

MutationObserver.min.js

37 ms

FormData.min.js

FormData.min.js

22 ms

tooltip.html

tooltip.html

22 ms

print.css

print.css

19 ms

loader.min.js

loader.min.js

24 ms

page-cache.min.js

page-cache.min.js

15 ms

navigation-menu.min.js

navigation-menu.min.js

24 ms

app.min.js

app.min.js

23 ms

validation.min.js

validation.min.js

22 ms

trim-input.min.js

trim-input.min.js

54 ms

cookies.min.js

cookies.min.js

29 ms

section-config.min.js

section-config.min.js

28 ms

invalidation-processor.min.js

invalidation-processor.min.js

32 ms

form-mini.min.js

form-mini.min.js

34 ms

form-mini-mixin.min.js

form-mini-mixin.min.js

44 ms

customer-data.min.js

customer-data.min.js

54 ms

customer-data-mixin.min.js

customer-data-mixin.min.js

47 ms

validation.min.js

validation.min.js

29 ms

menu.min.js

menu.min.js

41 ms

types.min.js

types.min.js

32 ms

layout.min.js

layout.min.js

48 ms

element.min.js

element.min.js

45 ms

jquery.validate.min.js

jquery.validate.min.js

38 ms

url.min.js

url.min.js

20 ms

storage.min.js

storage.min.js

35 ms

Accessibility Review

cameronpetersfloraldesign.com accessibility score

98

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.

Best Practices

cameronpetersfloraldesign.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cameronpetersfloraldesign.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 doesn't use 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 Cameronpetersfloraldesign.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 Cameronpetersfloraldesign.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

cameronpetersfloraldesign.com

Open Graph description is not detected on the main page of Cameron Peters Floral Design. 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: