Tools & Wizards About Us
fullblooms.co.uk screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fullblooms.co.uk

Page Load Speed

4.4 sec in total

First Response

328 ms

Resources Loaded

3.5 sec

Page Rendered

599 ms

fullblooms.co.uk screenshot

About Website

Visit fullblooms.co.uk now to see the best up-to-date Fullblooms content and also check out these interesting facts you probably never knew about fullblooms.co.uk

Same day flower delivery Liskeard by Full Blooms Florist your local flower shop. Send a bouquet, wedding flowers and tribute flowers for funerals. Order online anytime, visit or telephone the shop in ...

Visit fullblooms.co.uk

Key Findings

We analyzed Fullblooms.co.uk page load time and found that the first response time was 328 ms and then it took 4.1 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

fullblooms.co.uk performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

fullblooms.co.uk

328 ms

www.fullblooms.co.uk

434 ms

default.aspx

941 ms

jquery.min.js

33 ms

StyleSheet.css

477 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 88% of them (45 requests) were addressed to the original Fullblooms.co.uk, 4% (2 requests) were made to Maxcdn.bootstrapcdn.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Fullblooms.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.1 kB (12%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fullblooms.co.uk 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. 35% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 112.8 kB

  • Original 138.8 kB
  • After minification 134.8 kB
  • After compression 26.1 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 112.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 20.5 kB

  • Original 1.0 MB
  • After minification 994.8 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. Fullblooms images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 5.0 kB

  • Original 105.9 kB
  • After minification 105.9 kB
  • After compression 100.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. This website has mostly compressed JavaScripts.

CSS Optimization

-35%

Potential reduce by 15.8 kB

  • Original 45.4 kB
  • After minification 45.4 kB
  • After compression 29.6 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. Fullblooms.co.uk needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (51%)

Requests Now

43

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fullblooms.co.uk

fullblooms.co.uk

328 ms

www.fullblooms.co.uk

www.fullblooms.co.uk

434 ms

default.aspx

default.aspx

941 ms

jquery.min.js

jquery.min.js

33 ms

StyleSheet.css

StyleSheet.css

477 ms

magnific-popup.css

magnific-popup.css

63 ms

WebResource.axd

WebResource.axd

205 ms

StyleSheet.css

StyleSheet.css

23 ms

StyleSheetTheme6225569.css

StyleSheetTheme6225569.css

402 ms

WebResource.axd

WebResource.axd

139 ms

ScriptResource.axd

ScriptResource.axd

139 ms

ScriptResource.axd

ScriptResource.axd

137 ms

ScriptResource.axd

ScriptResource.axd

236 ms

ScriptResource.axd

ScriptResource.axd

237 ms

ScriptResource.axd

ScriptResource.axd

218 ms

ScriptResource.axd

ScriptResource.axd

222 ms

ScriptResource.axd

ScriptResource.axd

305 ms

ScriptResource.axd

ScriptResource.axd

312 ms

ScriptResource.axd

ScriptResource.axd

317 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

759 ms

element.js

element.js

91 ms

_Incapsula_Resource

_Incapsula_Resource

328 ms

font-awesome.min.css

font-awesome.min.css

91 ms

css

css

120 ms

css2

css2

133 ms

smartphoneBannerNew.png

smartphoneBannerNew.png

593 ms

Search.png

Search.png

183 ms

1867781528thumb.jpg

1867781528thumb.jpg

179 ms

btnProductSummaryBuy.png

btnProductSummaryBuy.png

580 ms

btnProductSummaryMore.png

btnProductSummaryMore.png

183 ms

1867781533thumb.jpg

1867781533thumb.jpg

253 ms

1867781496thumb.jpg

1867781496thumb.jpg

407 ms

1867781511thumb.jpg

1867781511thumb.jpg

584 ms

floristWindowLogoBlack.png

floristWindowLogoBlack.png

340 ms

facebookLarge.png

facebookLarge.png

580 ms

twitterLarge.png

twitterLarge.png

579 ms

PinterestLarge.png

PinterestLarge.png

580 ms

gPlacesLarge.png

gPlacesLarge.png

581 ms

smartphoneFloristWindowBlack.png

smartphoneFloristWindowBlack.png

584 ms

headerBgNew3.png

headerBgNew3.png

407 ms

bannerImageFB.png

bannerImageFB.png

574 ms

favicon.ico

favicon.ico

431 ms

slide1New.jpg

slide1New.jpg

926 ms

slide2New.jpg

slide2New.jpg

670 ms

Helvetica-Neue-Light22503.woff

Helvetica-Neue-Light22503.woff

587 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

29 ms

subset-FontAwesome5Free-Solid.woff

subset-FontAwesome5Free-Solid.woff

450 ms

_Incapsula_Resource

_Incapsula_Resource

43 ms

StyleSheetMobile.css

StyleSheetMobile.css

114 ms

StyleSheetMobile.css

StyleSheetMobile.css

26 ms

StyleSheetMobileOverride.css

StyleSheetMobileOverride.css

87 ms

Accessibility Review

fullblooms.co.uk accessibility score

65

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

fullblooms.co.uk best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fullblooms.co.uk SEO score

92

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fullblooms.co.uk can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fullblooms.co.uk 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

fullblooms.co.uk

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