Tools & Wizards About Us
springsinbloom.net screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

springsinbloom.net

Flower Delivery in Colorado Springs : Springs in Bloom Delivers Fresh Flowers Daily

Page Load Speed

1.2 sec in total

First Response

35 ms

Resources Loaded

862 ms

Page Rendered

343 ms

springsinbloom.net screenshot

About Website

Click here to check amazing Springs In Bloom content. Otherwise, check out these important facts you probably never knew about springsinbloom.net

Same day delivery by a professional florist in Colorado Springs, CO. Artistically designed flower arrangements for birthdays, anniversary, new baby, sympathy or any occasion. Springs in Bloom will del...

Visit springsinbloom.net

Key Findings

We analyzed Springsinbloom.net page load time and found that the first response time was 35 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

springsinbloom.net performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value1.5 s

99/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.233

53/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

springsinbloom.net

35 ms

www.springsinbloom.net

512 ms

base.css

10 ms

bootstrap-reduced.min.css

14 ms

styles.css

26 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original Springsinbloom.net, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (512 ms) belongs to the original domain Springsinbloom.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.5 kB (3%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 23.8 kB

  • Original 32.5 kB
  • After minification 30.8 kB
  • After compression 8.7 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 23.8 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 4.5 kB

  • Original 1.3 MB
  • After minification 1.3 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. Springs In Bloom images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 9.4 kB

  • Original 45.5 kB
  • After minification 45.3 kB
  • After compression 36.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 9.4 kB or 21% of the original size.

CSS Optimization

-3%

Potential reduce by 659 B

  • Original 20.0 kB
  • After minification 20.0 kB
  • After compression 19.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. Springsinbloom.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (31%)

Requests Now

26

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

springsinbloom.net

springsinbloom.net

35 ms

www.springsinbloom.net

www.springsinbloom.net

512 ms

base.css

base.css

10 ms

bootstrap-reduced.min.css

bootstrap-reduced.min.css

14 ms

styles.css

styles.css

26 ms

js

js

110 ms

font.css

font.css

10 ms

font.css

font.css

23 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

50 ms

utils.min.js

utils.min.js

9 ms

font-awesome.min.css

font-awesome.min.css

17 ms

embed

embed

247 ms

logo.png

logo.png

74 ms

70e9b20643d23756ac7723d565a7d3ec.250x154.png

70e9b20643d23756ac7723d565a7d3ec.250x154.png

73 ms

d6fe9ff02f6ce379e3c36ad1de6510b6.1200x371.jpg

d6fe9ff02f6ce379e3c36ad1de6510b6.1200x371.jpg

77 ms

25277d14a66fbac8e0f6ad0acf7110ad.340x372.jpg

25277d14a66fbac8e0f6ad0acf7110ad.340x372.jpg

75 ms

2ef6d8565844bcdae78a5e22d589cac7.340x421.jpg

2ef6d8565844bcdae78a5e22d589cac7.340x421.jpg

76 ms

3efbfae7b3edced0a261fa6b07de5a9d.340x372.jpg

3efbfae7b3edced0a261fa6b07de5a9d.340x372.jpg

74 ms

bba8f9bbd09a98cf66d9c352db7cb82f.340x564.jpg

bba8f9bbd09a98cf66d9c352db7cb82f.340x564.jpg

79 ms

94c16efe9f6d83abdbc6aa6531e89227.340x313.jpg

94c16efe9f6d83abdbc6aa6531e89227.340x313.jpg

75 ms

91ca3b388d9c2d102427e12f87f0c026.340x304.jpg

91ca3b388d9c2d102427e12f87f0c026.340x304.jpg

77 ms

84c258cbb693dd15ba4f3c5314f490f1.340x362.jpg

84c258cbb693dd15ba4f3c5314f490f1.340x362.jpg

78 ms

3f5b3b90fb649bc5b4126788e56e473b.340x293.jpg

3f5b3b90fb649bc5b4126788e56e473b.340x293.jpg

79 ms

powered-by-google.png

powered-by-google.png

119 ms

4c5073ed60992f40133ff2b73533a72b.40x40.a.png

4c5073ed60992f40133ff2b73533a72b.40x40.a.png

119 ms

b1a5999382be1b5d3f38e2792e68a240.40x40.a.png

b1a5999382be1b5d3f38e2792e68a240.40x40.a.png

119 ms

88aebb25402220357f628c08cb7e337f.40x40.a.png

88aebb25402220357f628c08cb7e337f.40x40.a.png

80 ms

nunito-sans-v6-latin-regular.woff

nunito-sans-v6-latin-regular.woff

80 ms

nunito-sans-v6-latin-300.woff

nunito-sans-v6-latin-300.woff

80 ms

nunito-sans-v6-latin-200.woff

nunito-sans-v6-latin-200.woff

85 ms

nunito-sans-v6-latin-600.woff

nunito-sans-v6-latin-600.woff

86 ms

nunito-sans-v6-latin-700.woff

nunito-sans-v6-latin-700.woff

86 ms

nunito-sans-v6-latin-800.woff

nunito-sans-v6-latin-800.woff

87 ms

nunito-sans-v6-latin-900.woff

nunito-sans-v6-latin-900.woff

86 ms

crimson-text-v11-latin-regular.woff

crimson-text-v11-latin-regular.woff

26 ms

crimson-text-v11-latin-600.woff

crimson-text-v11-latin-600.woff

27 ms

crimson-text-v11-latin-700.woff

crimson-text-v11-latin-700.woff

34 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

34 ms

js

js

36 ms

Accessibility Review

springsinbloom.net accessibility score

42

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

Image elements do not have [alt] attributes

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

springsinbloom.net best practices score

75

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

SEO Factors

springsinbloom.net SEO score

91

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Springsinbloom.net 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 Springsinbloom.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

springsinbloom.net

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