Tools & Wizards About Us
cambridgefloral.net screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

cambridgefloral.net

Cambridge Florist | Flower Delivery by Cambridge Floral

Page Load Speed

2.6 sec in total

First Response

41 ms

Resources Loaded

1.9 sec

Page Rendered

631 ms

cambridgefloral.net screenshot

About Website

Click here to check amazing Cambridge Floral content. Otherwise, check out these important facts you probably never knew about cambridgefloral.net

Best Cambridge florist. Cambridge Floral offers fresh flower delivery Cambridge. Save money by sending flowers directly with a Local Florist.

Visit cambridgefloral.net

Key Findings

We analyzed Cambridgefloral.net page load time and found that the first response time was 41 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

cambridgefloral.net performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

cambridgefloral.net

41 ms

www.cambridgefloral.net

408 ms

style.min.css

85 ms

ExitIntent.min.css

82 ms

toastr.min.css

73 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Cambridgefloral.net, 57% (34 requests) were made to Res.cloudinary.com and 35% (21 requests) were made to Hana-cdn-g9fcbgbya0azddab.a01.azurefd.net. The less responsive or slowest element that took the longest time to load (582 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.3 kB (7%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cambridgefloral.net main page is 2.5 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. 50% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 122.4 kB

  • Original 136.3 kB
  • After minification 84.0 kB
  • After compression 13.9 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 52.3 kB, which is 38% 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 122.4 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 6.9 kB

  • Original 2.1 MB
  • After minification 2.1 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. Cambridge Floral images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 40.7 kB

  • Original 252.9 kB
  • After minification 252.9 kB
  • After compression 212.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 40.7 kB or 16% of the original size.

CSS Optimization

-20%

Potential reduce by 11.3 kB

  • Original 55.4 kB
  • After minification 55.4 kB
  • After compression 44.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. Cambridgefloral.net needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (33%)

Requests Now

58

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cambridgefloral.net

cambridgefloral.net

41 ms

www.cambridgefloral.net

www.cambridgefloral.net

408 ms

style.min.css

style.min.css

85 ms

ExitIntent.min.css

ExitIntent.min.css

82 ms

toastr.min.css

toastr.min.css

73 ms

labs.min.css

labs.min.css

322 ms

masonry.min.css

masonry.min.css

102 ms

BannerModel.min.css

BannerModel.min.css

80 ms

zhjsyzln87hwzg1kioa5.jpg

zhjsyzln87hwzg1kioa5.jpg

108 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

105 ms

jquery-ui.min.js

jquery-ui.min.js

124 ms

bootstrap.min.js

bootstrap.min.js

93 ms

handlebars-v4.0.5.min.js

handlebars-v4.0.5.min.js

411 ms

handlebars-custom.min.js

handlebars-custom.min.js

99 ms

jquery.elevatezoom.min.js

jquery.elevatezoom.min.js

100 ms

fancybox.pack.min.js

fancybox.pack.min.js

107 ms

owl.carousel.min.js

owl.carousel.min.js

112 ms

sweetalert.min.js

sweetalert.min.js

108 ms

lazysizes.min.js

lazysizes.min.js

116 ms

cloudinary-core-shrinkwrap.min.js

cloudinary-core-shrinkwrap.min.js

126 ms

toastr.min.js

toastr.min.js

119 ms

jquery.exitintent.min.js

jquery.exitintent.min.js

123 ms

Global.min.js

Global.min.js

130 ms

_CommonHome.min.js

_CommonHome.min.js

127 ms

prev.png

prev.png

26 ms

next.png

next.png

84 ms

EcommLoader.gif

EcommLoader.gif

87 ms

cztnvk28o30juenxms6q.jpg

cztnvk28o30juenxms6q.jpg

270 ms

vkxozkprio6vgx5qgqod.png

vkxozkprio6vgx5qgqod.png

130 ms

kw8ipkvfxua55lustecc.png

kw8ipkvfxua55lustecc.png

105 ms

vanimqzoa7pryuso3sck.jpg

vanimqzoa7pryuso3sck.jpg

99 ms

vsdufjcuvqqvndxmvlou.jpg

vsdufjcuvqqvndxmvlou.jpg

236 ms

jhvnnrjjpocokegqk4zf.png

jhvnnrjjpocokegqk4zf.png

81 ms

qghokq9erpngoo0veann.jpg

qghokq9erpngoo0veann.jpg

176 ms

kmcnp2zyr93jlfa45nif.jpg

kmcnp2zyr93jlfa45nif.jpg

209 ms

tptggfeskevzv5pwm50m.jpg

tptggfeskevzv5pwm50m.jpg

131 ms

lblu6jpyvajfyljkkpey.png

lblu6jpyvajfyljkkpey.png

95 ms

z9wik8sgsqh9sknxrlkw.jpg

z9wik8sgsqh9sknxrlkw.jpg

87 ms

qwgzs3u86twqidxfath9.jpg

qwgzs3u86twqidxfath9.jpg

185 ms

ypik50gidmvdto57fdw6.jpg

ypik50gidmvdto57fdw6.jpg

333 ms

fqflyo5ku3equdgplyng.png

fqflyo5ku3equdgplyng.png

243 ms

cissxgisdnxmh2anarer.jpg

cissxgisdnxmh2anarer.jpg

275 ms

xikcdoznisvmmx4ot7hj.jpg

xikcdoznisvmmx4ot7hj.jpg

303 ms

k1a3dqgvpaz8k6i8shnp.jpg

k1a3dqgvpaz8k6i8shnp.jpg

285 ms

hajrppf3xaxaxdh84y64.jpg

hajrppf3xaxaxdh84y64.jpg

372 ms

et7kqfo8ltjiqlfi4ptw.jpg

et7kqfo8ltjiqlfi4ptw.jpg

410 ms

jbx4yhz4cwvn2yeeibgh.jpg

jbx4yhz4cwvn2yeeibgh.jpg

459 ms

juewlrnygdndc62k43uc.jpg

juewlrnygdndc62k43uc.jpg

437 ms

lnmoqbb9jse2bhbfmp7t.jpg

lnmoqbb9jse2bhbfmp7t.jpg

418 ms

hw0pddgoxpqunlu5cucz.jpg

hw0pddgoxpqunlu5cucz.jpg

506 ms

o3trmchxdcjs8lt8ydcq.jpg

o3trmchxdcjs8lt8ydcq.jpg

480 ms

x3wya2jvd8cer6cz75sa.jpg

x3wya2jvd8cer6cz75sa.jpg

582 ms

qghokq9erpngoo0veann.jpg

qghokq9erpngoo0veann.jpg

387 ms

tptggfeskevzv5pwm50m.jpg

tptggfeskevzv5pwm50m.jpg

372 ms

lblu6jpyvajfyljkkpey.png

lblu6jpyvajfyljkkpey.png

395 ms

z9wik8sgsqh9sknxrlkw.jpg

z9wik8sgsqh9sknxrlkw.jpg

445 ms

kmcnp2zyr93jlfa45nif.jpg

kmcnp2zyr93jlfa45nif.jpg

414 ms

qwgzs3u86twqidxfath9.jpg

qwgzs3u86twqidxfath9.jpg

499 ms

fqflyo5ku3equdgplyng.png

fqflyo5ku3equdgplyng.png

581 ms

ypik50gidmvdto57fdw6.jpg

ypik50gidmvdto57fdw6.jpg

278 ms

Accessibility Review

cambridgefloral.net accessibility score

83

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

cambridgefloral.net 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

cambridgefloral.net SEO score

90

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 uses legible font sizes

High

Tap targets are not sized appropriately

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 Cambridgefloral.net 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 Cambridgefloral.net 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

cambridgefloral.net

Open Graph data is detected on the main page of Cambridge Floral. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: