Tools & Wizards About Us
stewartcompounding.com screenshot

Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

stewartcompounding.com

Page Load Speed

586 ms in total

First Response

86 ms

Resources Loaded

396 ms

Page Rendered

104 ms

stewartcompounding.com screenshot

About Website

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

Stewart Compounding Pharmacy in Fayetteville, NC offers a wide variety of custom pharmaceutical prescription compounding with personalized customer care!

Visit stewartcompounding.com

Key Findings

We analyzed Stewartcompounding.com page load time and found that the first response time was 86 ms and then it took 500 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

stewartcompounding.com performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

stewartcompounding.com

86 ms

www.stewartcompounding.com

78 ms

stylesheet.css

32 ms

image-slideshow.js

60 ms

image-preloader.js

61 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 86% of them (19 requests) were addressed to the original Stewartcompounding.com, 9% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (157 ms) belongs to the original domain Stewartcompounding.com.

Page Optimization Overview & Recommendations

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

Content Size

674.0 kB

After Optimization

656.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stewartcompounding.com main page is 674.0 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. 25% of websites need less resources to load. Images take 632.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 12.3 kB

  • Original 15.8 kB
  • After minification 14.1 kB
  • After compression 3.5 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 1.7 kB, which is 11% 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 12.3 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 4.5 kB

  • Original 632.5 kB
  • After minification 628.0 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. Stewartcompounding images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 930 B

  • Original 24.4 kB
  • After minification 24.4 kB
  • After compression 23.5 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

-14%

Potential reduce by 190 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.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. Stewartcompounding.com needs all CSS files to be minified and compressed as it can save up to 190 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (20%)

Requests Now

20

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stewartcompounding.com

stewartcompounding.com

86 ms

www.stewartcompounding.com

www.stewartcompounding.com

78 ms

stylesheet.css

stylesheet.css

32 ms

image-slideshow.js

image-slideshow.js

60 ms

image-preloader.js

image-preloader.js

61 ms

dropdown-menu.js

dropdown-menu.js

62 ms

analytics.js

analytics.js

13 ms

background-page-top-gradiant.jpg

background-page-top-gradiant.jpg

37 ms

logo-stewart-compounding-pharmacy.gif

logo-stewart-compounding-pharmacy.gif

38 ms

logo-facebook.png

logo-facebook.png

37 ms

background-phone-number-container.gif

background-phone-number-container.gif

37 ms

background-top-navigation.jpg

background-top-navigation.jpg

66 ms

header-image-home-sterile.png

header-image-home-sterile.png

138 ms

header-image-home-bio-identical.png

header-image-home-bio-identical.png

157 ms

header-image-home-vet.png

header-image-home-vet.png

157 ms

background-contact-form-gradiant.jpg

background-contact-form-gradiant.jpg

69 ms

home-ad-nutrional.png

home-ad-nutrional.png

137 ms

home-ad-refills.png

home-ad-refills.png

137 ms

home-ad-pain.png

home-ad-pain.png

137 ms

logo-trimark-small.gif

logo-trimark-small.gif

151 ms

collect

collect

29 ms

js

js

55 ms

Accessibility Review

stewartcompounding.com accessibility score

49

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

stewartcompounding.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

stewartcompounding.com SEO score

69

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

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 Stewartcompounding.com 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 Stewartcompounding.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

stewartcompounding.com

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