22.8 sec in total
2 sec
20.5 sec
287 ms
Welcome to familyotc.com homepage info - get ready to check FamilyOTC best content for United States right away, or after learning these important things about familyotc.com
FamilyOTC - Your One Stop Shop for Everything OTC
Visit familyotc.comWe analyzed Familyotc.com page load time and found that the first response time was 2 sec and then it took 20.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
familyotc.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value32.1 s
0/100
25%
Value13.5 s
2/100
10%
Value5,710 ms
0/100
30%
Value0.708
7/100
15%
Value31.2 s
0/100
10%
2017 ms
100 ms
237 ms
255 ms
224 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 57% of them (60 requests) were addressed to the original Familyotc.com, 11% (12 requests) were made to Cdn3.volusion.com and 4% (4 requests) were made to Staticw2.yotpo.com. The less responsive or slowest element that took the longest time to load (15.1 sec) relates to the external source Upfront.thefind.com.
Page size can be reduced by 396.8 kB (36%)
1.1 MB
713.2 kB
In fact, the total size of Familyotc.com main page is 1.1 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. 55% of websites need less resources to load. Images take 503.7 kB which makes up the majority of the site volume.
Potential reduce by 160.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 160.1 kB or 81% of the original size.
Potential reduce by 67.6 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, FamilyOTC needs image optimization as it can save up to 67.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 146.2 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 146.2 kB or 39% of the original size.
Potential reduce by 23.0 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. Familyotc.com needs all CSS files to be minified and compressed as it can save up to 23.0 kB or 70% of the original size.
Number of requests can be reduced by 53 (54%)
98
45
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FamilyOTC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
Default.asp
2017 ms
jquery.min.js
100 ms
jquery-ui.min.js
237 ms
jquery-ui.css
255 ms
default.css
224 ms
volusion.js
224 ms
javascripts.js
3619 ms
Imports.css
223 ms
jquery.min.js
363 ms
element.js
228 ms
style.css
760 ms
jquery.js
569 ms
wowslider.js
321 ms
script.js
422 ms
seal.js
217 ms
conversion.js
112 ms
Colors.css
77 ms
Content_Area.css
78 ms
Template.css
157 ms
Navigation.css
79 ms
ga.js
149 ms
analytics.js
151 ms
80f3c25986847d4cdaa287fe018a412a.png
15124 ms
verification_seal.gif
220 ms
CD4146049-1.jpg
232 ms
CD4061727-1.jpg
476 ms
CD3293396-1.jpg
477 ms
CD4230280-1.jpg
467 ms
CD3374774-1.jpg
476 ms
CD4452926-1.jpg
487 ms
CD3948239-1.jpg
485 ms
CD5205026-1.jpg
482 ms
CD4587507-1.jpg
609 ms
CD4538294-1.jpg
610 ms
CD5053335-1.jpg
611 ms
CD4794053-1.jpg
530 ms
nav-divider.png
208 ms
familyotc.png
209 ms
message.gif
478 ms
minibasket-bg.png
209 ms
but-checkout.png
202 ms
nav-bg.gif
203 ms
searchbar-bg.gif
215 ms
search-ttl.gif
214 ms
searchfield-bg.png
213 ms
but-go.png
214 ms
left_nav_tile.gif
207 ms
lftnavtop.gif
263 ms
Menu1_Bullet.gif
258 ms
arthritis.gif
260 ms
baby.gif
259 ms
beauty.gif
261 ms
diabetic.gif
453 ms
supplements.gif
455 ms
household.gif
454 ms
personalcare.gif
455 ms
remedies.gif
455 ms
sexual.gif
462 ms
vitamins.gif
461 ms
pets.gif
462 ms
SavingsCenter.gif
463 ms
CD4913372-A.jpg
462 ms
NexiumOTC.jpg
505 ms
payments2.jpg
506 ms
seal_volusion2.png
506 ms
goldbond2.jpg
706 ms
allergies.jpg
1242 ms
crest_3d_white.jpg
701 ms
newwaldenfarms.jpg
945 ms
alivevitamins.jpg
791 ms
goldbond2.jpg
596 ms
allergies.jpg
574 ms
ecommerce.js
38 ms
collect
23 ms
crest_3d_white.jpg
568 ms
newwaldenfarms.jpg
603 ms
alivevitamins.jpg
601 ms
clear1x1.gif
636 ms
Icon_FreeShipping_Small.gif
693 ms
bg_lftnav.png
688 ms
collect
94 ms
translateelement.css
92 ms
main.js
229 ms
upfront-badgeinit.js
14704 ms
secure90x72.gif
61 ms
element_main.js
108 ms
bullet.png
386 ms
bg.png
634 ms
pause.png
389 ms
Grid_Divider_Vertical.gif
386 ms
Grid_Divider_Horizontal.gif
327 ms
seal_1843926.js
86 ms
130 ms
widget.js
70 ms
widget.css
186 ms
221 ms
i
123 ms
batch
216 ms
css
176 ms
sign_in_url
106 ms
badges-500.png
102 ms
translate_24dp.png
96 ms
l
81 ms
googlelogo_color_42x16dp.png
119 ms
yotpo-widget-font.svg
8 ms
yotpo-widget-font.woff
43 ms
familyotc.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
familyotc.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
familyotc.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
EN
![]()
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familyotc.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 Familyotc.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
familyotc.com
Open Graph description is not detected on the main page of FamilyOTC. 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: