99.7 sec in total
369 ms
42.8 sec
56.5 sec
Visit flor.com now to see the best up-to-date FLOR content for United States and also check out these interesting facts you probably never knew about flor.com
FLOR's modern carpet tiles allow you to create custom, unique area rugs that are as durable as they are stylish. Design your perfect rug with FLOR.
Visit flor.comWe analyzed Flor.com page load time and found that the first response time was 369 ms and then it took 99.3 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.
flor.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value15.5 s
0/100
25%
Value9.4 s
12/100
10%
Value2,920 ms
3/100
30%
Value0
100/100
15%
Value24.5 s
0/100
10%
369 ms
1057 ms
519 ms
686 ms
1606 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 49% of them (45 requests) were addressed to the original Flor.com, 4% (4 requests) were made to Google-analytics.com and 3% (3 requests) were made to Js.bronto.com. The less responsive or slowest element that took the longest time to load (12.2 sec) relates to the external source Vars.hotjar.com.
Page size can be reduced by 1.2 MB (9%)
14.0 MB
12.8 MB
In fact, the total size of Flor.com main page is 14.0 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. 85% 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. Images take 12.4 MB which makes up the majority of the site volume.
Potential reduce by 150.9 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 150.9 kB or 81% of the original size.
Potential reduce by 51.8 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. FLOR images are well optimized though.
Potential reduce by 718.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 718.6 kB or 65% of the original size.
Potential reduce by 294.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. Flor.com needs all CSS files to be minified and compressed as it can save up to 294.0 kB or 86% of the original size.
Number of requests can be reduced by 38 (47%)
81
43
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLOR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
flor.com
369 ms
www.flor.com
1057 ms
308feb
519 ms
0ea5f5f13e2cbc967df995c0cfd3e07d.css
686 ms
b69ea2fea877efbd68c469fa4ba21377.js
1606 ms
21ec1b881d504cc7f854db88bc32c9fc.css
1319 ms
flor-2.min.js
1325 ms
seal.js
6029 ms
bta.js
4755 ms
flor.svg
1273 ms
051717_Kensington_Promobox.jpg
1328 ms
051717_PR_promobox.jpg
1226 ms
051717_SundialSundae_PromoBox.jpg
2096 ms
051717_SupperClub_PromoBox.jpg
2071 ms
home-banner.gif
6163 ms
start-from-scratch.png
2848 ms
Tailor-Rug-Design.png
2848 ms
Browse-Area-Rugs.png
2849 ms
Parallel_Reality_1920x774.jpg
4299 ms
MadeYouLook_1920x774.jpg
4241 ms
Reoriented_1920x774.jpg
4508 ms
store-locator-banner.jpg
3405 ms
ajax-loader.gif
2849 ms
050117_767x767_DaybreakDance.jpg
4238 ms
050117_767x767_SeaSide.jpg
4239 ms
050117_767x767_Starburst.jpg
4562 ms
050117_767x767_LetsVacation.jpg
5805 ms
050117_767x767_SodaShoppe.jpg
5589 ms
050117_767x767_AerialView.jpg
5591 ms
050117_767x767_BippityBoppity.jpg
5592 ms
050117_767x767_SecretGarden.jpg
5721 ms
050117_767x767_ModernMix.jpg
6054 ms
NewWitDTop.jpg
5942 ms
Movable.png
5710 ms
durable.png
5669 ms
washable.png
6074 ms
Recyclable.png
6073 ms
lovable.png
5884 ms
footer-left-bg.png
5888 ms
footer-right-bg.png
5936 ms
gtm.js
1674 ms
ReplicaStd.woff
4650 ms
hotjar-488075.js
3607 ms
dc.js
5147 ms
b.min.js
11587 ms
flor.netmng.com
11982 ms
fbevents.js
5871 ms
delivery.js
11944 ms
quant.js
11943 ms
bat.js
11943 ms
analytics.js
10992 ms
WorchesterEF-Medium.woff
8065 ms
ReplicaStd-Bold.woff
8065 ms
ReplicaStd-Light.woff
8065 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
11651 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
12236 ms
email.png
6642 ms
ReplicaPro-Bold.woff
6820 ms
entrust_site_seal.png
9317 ms
WorchesterEF-DemiBold.woff
5553 ms
701503539904803
5027 ms
b.min.js
4609 ms
1152 ms
create.html
7312 ms
ct.pinterest.com
8935 ms
floricons.woff
3946 ms
jquery.min.js
6306 ms
js
2316 ms
rules-p-52VuZpB6VDVRs.js
8355 ms
5584 ms
flor.netmng.com
2578 ms
src=5238131;type=invmedia;cat=rlzt06ol;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=1
7335 ms
Pug
7574 ms
collect
3150 ms
collect
4042 ms
visit-data
5970 ms
config.js
3117 ms
pixel;r=1778700262;rf=0;a=p-52VuZpB6VDVRs;url=https%3A%2F%2Fwww.flor.com%2F;fpan=1;fpa=P0-2035314173-1504637942120;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504637942120;tzo=-180;ogl=
4384 ms
ga-audiences
2359 ms
tap.php
1501 ms
rum
1499 ms
13209
2950 ms
sync
1318 ms
382706.gif
1076 ms
px
1076 ms
sd
1076 ms
visit-data
1242 ms
709 ms
24 ms
nr-1044.min.js
215 ms
polyfills.js
148 ms
config.js
5 ms
flor.com accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
No form fields have multiple labels
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
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.
flor.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
flor.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flor.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 Flor.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.
flor.com
Open Graph description is not detected on the main page of FLOR. 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: