Tools & Wizards About Us
fluticare.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

fluticare.com

FlutiCare® 24-Hour Allergy Symptom Relief – Aytu Health

Page Load Speed

4.9 sec in total

First Response

213 ms

Resources Loaded

1.7 sec

Page Rendered

3.1 sec

fluticare.com screenshot

About Website

Visit fluticare.com now to see the best up-to-date Fluti Care content and also check out these interesting facts you probably never knew about fluticare.com

About The Product Once-daily FlutiCare® Allergy Relieving Nasal Spray is proven to offer 24-hour relief of both nose and sinus-related allergy symptoms. Full prescription-strength FlutiCare® Allergy R...

Visit fluticare.com

Key Findings

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

Performance Metrics

fluticare.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

fluticare-nasal-allergy-spray-24-hour-relief

213 ms

triplepx.txt

191 ms

styles.css

385 ms

load_feature-ab38017af3cf759db0af0bbd1e75229f6a189f5bf1f2db42169630998b969021.js

416 ms

features-87e8399988880142f2c62771b9d8f2ff6c290b3ff745dd426eb0dfe0db9d1dae.js

407 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fluticare.com, 7% (2 requests) were made to Googletagmanager.com and 7% (2 requests) were made to Seal-alaskaoregonwesternwashington.bbb.org. The less responsive or slowest element that took the longest time to load (479 ms) relates to the external source D1um8515vdn9kb.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.5 kB (77%)

Content Size

253.1 kB

After Optimization

57.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fluticare.com main page is 253.1 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. 40% of websites need less resources to load. HTML takes 242.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 194.8 kB

  • Original 242.7 kB
  • After minification 232.1 kB
  • After compression 47.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. 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 194.8 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 648 B

  • Original 7.0 kB
  • After minification 6.3 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. Fluti Care images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 23 B

  • Original 3.5 kB
  • After minification 3.5 kB
  • After compression 3.4 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.

Requests Breakdown

Number of requests can be reduced by 6 (60%)

Requests Now

10

After Optimization

4

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

fluticare-nasal-allergy-spray-24-hour-relief

fluticare-nasal-allergy-spray-24-hour-relief

213 ms

triplepx.txt

triplepx.txt

191 ms

styles.css

styles.css

385 ms

load_feature-ab38017af3cf759db0af0bbd1e75229f6a189f5bf1f2db42169630998b969021.js

load_feature-ab38017af3cf759db0af0bbd1e75229f6a189f5bf1f2db42169630998b969021.js

416 ms

features-87e8399988880142f2c62771b9d8f2ff6c290b3ff745dd426eb0dfe0db9d1dae.js

features-87e8399988880142f2c62771b9d8f2ff6c290b3ff745dd426eb0dfe0db9d1dae.js

407 ms

scripts.js

scripts.js

406 ms

cscode_discount_js.js

cscode_discount_js.js

405 ms

vendor.min.js

vendor.min.js

403 ms

theme.js

theme.js

403 ms

gempagev2.js

gempagev2.js

479 ms

cscode_discount_css.css

cscode_discount_css.css

402 ms

cscode_discount_js.js

cscode_discount_js.js

401 ms

gtm.js

gtm.js

176 ms

trekkie.storefront.e695302c3cd17296c85e559451c496db44e32e17.min.js

trekkie.storefront.e695302c3cd17296c85e559451c496db44e32e17.min.js

82 ms

shop_events_listener-65cd0ba3fcd81a1df33f2510ec5bcf8c0e0958653b50e3965ec972dd638ee13f.js

shop_events_listener-65cd0ba3fcd81a1df33f2510ec5bcf8c0e0958653b50e3965ec972dd638ee13f.js

81 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

75 ms

browser.js

browser.js

86 ms

blue-seal-200-42-bbb-90278992.png

blue-seal-200-42-bbb-90278992.png

259 ms

badge-7-bbb-90278992.png

badge-7-bbb-90278992.png

296 ms

aytu-cons-hlth-logo_1_450x.png

aytu-cons-hlth-logo_1_450x.png

85 ms

trekkie.storefront.e695302c3cd17296c85e559451c496db44e32e17.min.js

trekkie.storefront.e695302c3cd17296c85e559451c496db44e32e17.min.js

71 ms

produce

produce

94 ms

track.js

track.js

464 ms

4b805c0f-9c91-44fa-8457-4b2e1c138863.js

4b805c0f-9c91-44fa-8457-4b2e1c138863.js

386 ms

js

js

63 ms

aftersell_sdk.bundle.min.js

aftersell_sdk.bundle.min.js

288 ms

appstle-init.js

appstle-init.js

142 ms

klaviyo.js

klaviyo.js

139 ms

aytuhealth.js

aytuhealth.js

184 ms

Accessibility Review

fluticare.com accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

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

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

Links do not have a discernible name

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fluticare.com SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fluticare.com

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