3.2 sec in total
437 ms
2.7 sec
65 ms
Welcome to wellspringrx.com homepage info - get ready to check Wellspring Rx best content right away, or after learning these important things about wellspringrx.com
Wellspring Pharmacy in Oakland, CA goes the extra mile for our customers and health professionals to make your experience with our pharmacy special.
Visit wellspringrx.comWe analyzed Wellspringrx.com page load time and found that the first response time was 437 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wellspringrx.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value8.9 s
1/100
25%
Value7.6 s
25/100
10%
Value1,400 ms
16/100
30%
Value0.03
100/100
15%
Value14.0 s
10/100
10%
437 ms
69 ms
63 ms
941 ms
60 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Wellspringrx.com, 38% (15 requests) were made to Static.parastorage.com and 30% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (941 ms) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 536.0 kB (56%)
959.5 kB
423.5 kB
In fact, the total size of Wellspringrx.com main page is 959.5 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. 30% of websites need less resources to load. Javascripts take 484.8 kB which makes up the majority of the site volume.
Potential reduce by 283.4 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 283.4 kB or 75% of the original size.
Potential reduce by 23.9 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. Obviously, Wellspring Rx needs image optimization as it can save up to 23.9 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 228.8 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 228.8 kB or 47% of the original size.
Number of requests can be reduced by 10 (42%)
24
14
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wellspring Rx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.wellspringrx.com
437 ms
minified.js
69 ms
focus-within-polyfill.js
63 ms
polyfill.min.js
941 ms
thunderbolt-commons.c1d8ed1c.bundle.min.js
60 ms
main.4a2d1e74.bundle.min.js
108 ms
main.renderer.1d21f023.bundle.min.js
59 ms
lodash.min.js
108 ms
react.production.min.js
62 ms
react-dom.production.min.js
108 ms
siteTags.bundle.min.js
109 ms
logopng.png
269 ms
a8bc8a_1b95dac4e8d54a6cb08f24b53ab268eb~mv2_d_2000_1334_s_2.jpg
429 ms
0c7dfc_9f99d6d3e04d412687b79824aa83d62b~mv2.jpg
443 ms
0c7dfc_d78de89b03b04d778428be4c4d7101d4~mv2.png
428 ms
0c7dfc_39b4c2ce03e9494a838db47a30773496~mv2.jpg
445 ms
a8bc8a_83c38824f116431f9a318c759b2ea9c7~mv2.png
492 ms
a8bc8a_376e1aedefdc4faa983b6af120d33339~mv2.png
483 ms
a8bc8a_361d175976b249c1b2a43c1259d802d0~mv2.png
641 ms
a8bc8a_55e7a4da8cf54c35a739ea3bb616484f~mv2.png
646 ms
bundle.min.js
67 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
41 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
40 ms
388ef902-2c31-4818-abb1-a40dcd81f6d6.woff
41 ms
109 ms
107 ms
107 ms
108 ms
106 ms
104 ms
147 ms
143 ms
139 ms
141 ms
141 ms
138 ms
deprecation-en.v5.html
12 ms
bolt-performance
12 ms
deprecation-style.v5.css
7 ms
right-arrow.svg
4 ms
wellspringrx.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
wellspringrx.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wellspringrx.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wellspringrx.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 Wellspringrx.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.
wellspringrx.com
Open Graph data is detected on the main page of Wellspring Rx. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: