7.9 sec in total
130 ms
6.6 sec
1.2 sec
Visit foybs.com now to see the best up-to-date Foybs content for United States and also check out these interesting facts you probably never knew about foybs.com
Falls Are Serious and CostlyYou or your loved one have worked a life time expecting to be able to enjoy you late adult life with little or no unexpected events in later years. The fact is that falls ...
Visit foybs.comWe analyzed Foybs.com page load time and found that the first response time was 130 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
foybs.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value7.2 s
5/100
25%
Value5.3 s
57/100
10%
Value790 ms
37/100
30%
Value0.136
80/100
15%
Value7.4 s
48/100
10%
130 ms
2504 ms
260 ms
232 ms
201 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 68% of them (63 requests) were addressed to the original Foybs.com, 24% (22 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Foybs.com.
Page size can be reduced by 937.8 kB (74%)
1.3 MB
333.4 kB
In fact, the total size of Foybs.com main page is 1.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 584.7 kB which makes up the majority of the site volume.
Potential reduce by 83.8 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 83.8 kB or 83% of the original size.
Potential reduce by 1.5 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. Foybs images are well optimized though.
Potential reduce by 347.6 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 347.6 kB or 70% of the original size.
Potential reduce by 504.8 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. Foybs.com needs all CSS files to be minified and compressed as it can save up to 504.8 kB or 86% of the original size.
Number of requests can be reduced by 50 (77%)
65
15
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foybs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
foybs.com
130 ms
foybs.com
2504 ms
wp-emoji-release.min.js
260 ms
font-awesome.css
232 ms
frontend.plugins.min.css
201 ms
frontend.min.css
196 ms
woocommerce-layout.css
236 ms
woocommerce.css
390 ms
style.css
432 ms
css
521 ms
meanmenu.css
430 ms
slick.css
518 ms
icons.css
425 ms
font-awesome.min.css
426 ms
style.css
635 ms
masterslider.main.css
543 ms
custom.css
549 ms
fm-style-1.css
536 ms
css
634 ms
styles.min.css
549 ms
jquery.js
661 ms
jquery-migrate.min.js
762 ms
mediaelement-and-player.min.js
766 ms
mediaelement-migrate.min.js
764 ms
client_plugins.min.js
833 ms
widget.min.js
699 ms
effect.min.js
698 ms
effect-shake.min.js
854 ms
scripts.min.js
866 ms
fm-script-6.js
852 ms
css
598 ms
js
414 ms
wp-mediaelement.min.js
755 ms
imagesloaded.min.js
760 ms
masonry.min.js
752 ms
jquery.masonry.min.js
754 ms
client_frontend.min.js
753 ms
jquery.blockUI.min.js
839 ms
add-to-cart.min.js
841 ms
js.cookie.min.js
840 ms
woocommerce.min.js
842 ms
cart-fragments.min.js
818 ms
navigation.js
794 ms
skip-link-focus-fix.js
757 ms
jquery.meanmenu.js
728 ms
slick.js
731 ms
theia-sticky-sidebar.min.js
615 ms
custom.js
532 ms
jquery.easing.min.js
525 ms
masterslider.min.js
530 ms
jquery.prettyPhoto.min.js
443 ms
wp-embed.min.js
438 ms
logo-2.jpg
94 ms
blank.gif
83 ms
Lady-In-Walk-in-Bath-Tub.jpg
85 ms
LH-luxor.jpg
80 ms
end-cap.jpg
82 ms
analytics.js
832 ms
fontawesome-webfont.woff
830 ms
7cHpv4kjgoGqM7E_Ass8.ttf
1109 ms
7cHqv4kjgoGqM7E3_-gs6Vop.ttf
1110 ms
7cHqv4kjgoGqM7E3p-ks6Vop.ttf
1230 ms
7cHqv4kjgoGqM7E30-8s6Vop.ttf
1230 ms
7cHqv4kjgoGqM7E3t-4s6Vop.ttf
1310 ms
7cHqv4kjgoGqM7E3q-0s6Vop.ttf
1309 ms
foybs.com
2322 ms
loading-2.gif
399 ms
light-skin-6.png
398 ms
Slide3.png
505 ms
mem8YaGs126MiZpBA-UFW50e.ttf
303 ms
mem5YaGs126MiZpBA-UN_r8OXOhs.ttf
306 ms
mem5YaGs126MiZpBA-UNirkOXOhs.ttf
307 ms
mem5YaGs126MiZpBA-UN7rgOXOhs.ttf
307 ms
mem5YaGs126MiZpBA-UN8rsOXOhs.ttf
306 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf
307 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf
307 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf
308 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf
310 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf
309 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf
308 ms
S6u9w4BMUTPHh6UVSwaPHA.ttf
323 ms
S6u9w4BMUTPHh50XSwaPHA.ttf
322 ms
S6uyw4BMUTPHjxAwWw.ttf
322 ms
S6u9w4BMUTPHh7USSwaPHA.ttf
326 ms
S6u8w4BMUTPHh30AUi-v.ttf
326 ms
fontawesome-webfont.woff
321 ms
et-line.woff
300 ms
collect
204 ms
collect
212 ms
Slide2.png
55 ms
Slide1.png
56 ms
woocommerce-smallscreen.css
7 ms
foybs.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.
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
No form fields have multiple labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
foybs.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foybs.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 Foybs.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 Foybs.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.
foybs.com
Open Graph data is detected on the main page of Foybs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: