1.9 sec in total
20 ms
1.6 sec
319 ms
Visit fohm.com now to see the best up-to-date Fohm content for United States and also check out these interesting facts you probably never knew about fohm.com
Buy the domain name Fohm.com and launch your business with a premium domain and a high quality logo.
Visit fohm.comWe analyzed Fohm.com page load time and found that the first response time was 20 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
fohm.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value5.8 s
15/100
25%
Value4.2 s
77/100
10%
Value2,050 ms
7/100
30%
Value0.001
100/100
15%
Value15.2 s
7/100
10%
20 ms
67 ms
99 ms
100 ms
90 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fohm.com, 15% (8 requests) were made to Images-na.ssl-images-amazon.com and 8% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (218 ms) relates to the external source Static-na.payments-amazon.com.
Page size can be reduced by 852.8 kB (33%)
2.6 MB
1.7 MB
In fact, the total size of Fohm.com main page is 2.6 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 75.2 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 75.2 kB or 70% of the original size.
Potential reduce by 99.2 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. Fohm images are well optimized though.
Potential reduce by 436.1 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 436.1 kB or 63% of the original size.
Potential reduce by 242.3 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. Fohm.com needs all CSS files to be minified and compressed as it can save up to 242.3 kB or 86% of the original size.
Number of requests can be reduced by 25 (54%)
46
21
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fohm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
hibr.com
20 ms
hibr.com
67 ms
css
99 ms
style.css
100 ms
style.css
90 ms
jquery.min.js
122 ms
api.min.js
96 ms
devicepx-jetpack.js
83 ms
Widgets.js
218 ms
amazon-checkout.js
84 ms
flexslider-modified-min.js
86 ms
plugins-min.js
92 ms
app.js
92 ms
wp-embed.min.js
94 ms
add-to-cart-variation.min.js
95 ms
e-201611.js
93 ms
conversion.js
116 ms
analytics.js
106 ms
hibr-logo-new.svg
64 ms
mattress-pattern-vector.jpg
40 ms
hibr-mattress-vector.png
44 ms
home-pillow-slider.png
41 ms
home-slider-happy.png
50 ms
home-faux-slider.jpg
40 ms
box-mattress-cta.jpg
38 ms
box-pillow-cta.jpg
42 ms
kera.jpg
41 ms
giuli-box.jpg
44 ms
flag.jpg
47 ms
WooCommerce.woff
47 ms
login1.js
114 ms
ec.js
15 ms
84 ms
g.gif
61 ms
js
80 ms
collect
25 ms
collect
95 ms
widgets
106 ms
donations.css
58 ms
collect
29 ms
58 ms
collect
60 ms
gtmp_compiled_9-hatpZX8VY.js
48 ms
ga-audiences
29 ms
forester-client-978607279._V369474569_.js
26 ms
jserrors-1871966242._V375149216_.js
27 ms
ga-audiences
83 ms
spa-widget._V301868231_.css
15 ms
spa-library._V297680853_.js
20 ms
new-CommonWidgetLib._V296248717_.js
17 ms
spa-widget._V296248752_.js
17 ms
AGWSWK15IEJJ7:182-9444347-8441224:5J9750ZDKKGJKN2R7RWB$uedata=s:%2Fgp%2Fcba%2Fuedata%2F182-9444347-8441224%3Fld%26v%3D28%26id%3D5J9750ZDKKGJKN2R7RWB%26ifr%3D1%26sw%3D1024%26sh%3D768%26m%3D1%26sc%3D5J9750ZDKKGJKN2R7RWB%26ue%3D0%26bb%3D1%26be%3D72%26pc%3D79%26tc%3D-87%26na_%3D-87%26fe_%3D-87%26lk_%3D-87%26_lk%3D-87%26co_%3D-87%26_co%3D-87%26rq_%3D-87%26rs_%3D-87%26_rs%3D17%26dl_%3D-1%26di_%3D72%26de_%3D72%26_de%3D79%26_dc%3D79%26ld_%3D79%26ty%3D0%26rc%3D0%26hob%3D0%26hoe%3D0%26ld%3D80%26t%3D1458410195688%26ctb%3D1%26csmtags%3Dnonredirect%7CnoAmznJQ:80
124 ms
button.png
6 ms
fohm.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.
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
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
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.
fohm.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Browser errors were logged to the console
Page has valid source maps
fohm.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fohm.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 Fohm.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.
fohm.com
Open Graph data is detected on the main page of Fohm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: