4.3 sec in total
169 ms
2.9 sec
1.2 sec
Visit whytile.com now to see the best up-to-date Why Tile content and also check out these interesting facts you probably never knew about whytile.com
Why Tile® is the tile trade’s first-ever industry-wide initiative designed to provide what we hope will be the information you need to make the choice for tile a clear and easy one.
Visit whytile.comWe analyzed Whytile.com page load time and found that the first response time was 169 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
whytile.com performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value14.0 s
0/100
25%
Value14.3 s
1/100
10%
Value5,600 ms
0/100
30%
Value0.157
74/100
15%
Value25.0 s
0/100
10%
169 ms
217 ms
114 ms
95 ms
423 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 7% of them (10 requests) were addressed to the original Whytile.com, 71% (100 requests) were made to Whytile.wpenginepowered.com and 4% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Whytile.wpenginepowered.com.
Page size can be reduced by 218.8 kB (7%)
3.0 MB
2.7 MB
In fact, the total size of Whytile.com main page is 3.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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 198.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 198.4 kB or 86% of the original size.
Potential reduce by 0 B
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. Why Tile images are well optimized though.
Potential reduce by 13.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.5 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. Whytile.com has all CSS files already compressed.
Number of requests can be reduced by 52 (43%)
121
69
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Tile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
whytile.com
169 ms
whytile.com
217 ms
optimize.js
114 ms
css
95 ms
autoptimize_99598f29c0f55eb03df981784a3ccf11.css
423 ms
autoptimize_2181edd0266e714780909941cdca46ee.css
95 ms
jquery.min.js
111 ms
jquery-migrate.min.js
90 ms
autoptimize_single_3d0cc1804b5380d5036a599d5cfe90e7.js
94 ms
jquery.mousewheel.min.js
95 ms
jquery.mCustomScrollbar.min.js
109 ms
autoptimize_single_976f38344b39cab5bbd3ac72e1f527b8.js
106 ms
autoptimize_single_b04e2b157b41cc8804fe8d89eebe0f49.js
104 ms
autoptimize_single_49cea0a781874a962879c2caca9bc322.js
110 ms
jquery.json.min.js
138 ms
gravityforms.min.js
139 ms
utils.min.js
144 ms
above-the-fold.min.js
143 ms
klf0aie.css
100 ms
all.css
199 ms
js
98 ms
main.min.js
140 ms
core.min.js
139 ms
effect.min.js
139 ms
autoptimize_single_f0cba76b7742df5f4c51e5b1d106c1a7.js
153 ms
select2.full.min.js
151 ms
autoptimize_single_678a1177fbf0d3997250644c34adfb41.js
153 ms
wp-polyfill-inert.min.js
149 ms
regenerator-runtime.min.js
149 ms
wp-polyfill.min.js
160 ms
dom-ready.min.js
195 ms
hooks.min.js
162 ms
i18n.min.js
161 ms
a11y.min.js
163 ms
jquery.maskedinput.min.js
192 ms
placeholders.jquery.min.js
190 ms
vendor-theme.min.js
194 ms
scripts-theme.min.js
192 ms
legacy.min.js
193 ms
jquery-mousewheel.min.js
194 ms
custom-scrollbar.min.js
209 ms
post-type.min.js
208 ms
ubermenu.min.js
210 ms
js_composer_front.min.js
131 ms
autoptimize_single_91954b488a9bfcade528d6ff5c7ce83f.js
127 ms
gtm.js
43 ms
js
36 ms
p.css
30 ms
js
155 ms
analytics.js
144 ms
WhyTile.com_logo_R_160web.png
136 ms
Mg9VuFZ6Y4M
752 ms
hospitality-150x150.jpg
244 ms
retail-150x150.jpg
244 ms
corporate-150x150.jpg
201 ms
healthcare-150x150.jpg
196 ms
industrial-150x150.jpg
199 ms
multifamily-150x150.jpg
198 ms
public-150x150.jpg
683 ms
historical-150x150.jpg
684 ms
iStock-898206500-1-150x150.jpg
686 ms
bathroom-150x150.jpg
686 ms
CK_Circle_Thumbnail-150x150.jpg
747 ms
Schluter_SB-5-cropped-150x150.jpg
746 ms
y9-hxB-M-150x150.jpg
841 ms
iStock-171136254-150x150.jpg
840 ms
furniture-menu-item-150x150.jpg
841 ms
Circle-image-for-application-popup-page-500x500-30-150x150.jpg
840 ms
kitchen-150x150.jpg
841 ms
Hero-Image-150x150.jpg
819 ms
multipurpose-room-application-MR_1-150x150-2-150x150.jpg
1373 ms
Hero-Image-150x150.jpg
904 ms
iStock-648448920-150x150.jpg
903 ms
menu-icon-150x150.jpg
1375 ms
PR_CircleImage-150x150.jpeg
903 ms
iStock-951214224-150x150.jpg
905 ms
shower6-application-150x150.jpg
978 ms
pool4-150x150.jpg
977 ms
CLRA6IFn-150x150.jpg
976 ms
steam-room-nav.jpg
975 ms
ceramic-tile-material-comparison-150x150.jpeg
1381 ms
A306_r_Beach_House_Wood_Cream_living-150x150.jpg
1383 ms
sustainability-150x150.jpeg
1383 ms
hard-rock-hotel.jpg
1180 ms
xC104-BrightlineRailSystemTerminals_GRB1614.jpg
1182 ms
OceanReef5-copy-150x150.jpg
1370 ms
town-homes-06-150x150.jpg
1371 ms
d
108 ms
d
591 ms
d
594 ms
d
654 ms
ahcfv8qz1zt6hCC5G4F_P4ASlUuYo2DmYyU.ttf
812 ms
icomoon-the7-font.ttf
593 ms
my-social-icon.woff
814 ms
fa-solid-900.woff
591 ms
fa-solid-900.woff
1089 ms
fa-solid-900.woff
1089 ms
fa-regular-400.woff
748 ms
fa-regular-400.woff
810 ms
fa-regular-400.woff
810 ms
library-150x150.jpg
1279 ms
collect
491 ms
fa-brands-400.woff
708 ms
fa-brands-400.woff
988 ms
fa-brands-400.woff
1187 ms
gf-mmx-cremo_superiore_nero_damascato-_-_-300150-amb42-living-30.jpg
1180 ms
healthy_spaces_nav2.jpg
1192 ms
design_nav-opt.jpg
1179 ms
easy_care6.jpg
1136 ms
heritage_hp.jpg
1240 ms
pantone-blush-feature-image-listice-1-200x120.jpeg
1135 ms
pool-guide-featured-photo-why-tile-200x120.jpg
696 ms
collect
290 ms
featured-photo-for-why-tile-200x120.jpg
696 ms
FPO-interactive-image-home-main.jpg
696 ms
image-pin.png
697 ms
www-player.css
133 ms
www-embed-player.js
219 ms
base.js
292 ms
Whytile_icons-copy-2_0005_ZeroAllergens.jpg
638 ms
Whytile_icons-copy-2_0001_Ecofriendly.jpg
688 ms
Whytile_icons-copy-2_0000_SafeSecure.jpg
566 ms
A214_r_MoroccanHabitat_black-1043x691.jpg
643 ms
A214_r_MoroccanHabitat_fog-1043x691.jpg
645 ms
A214_r_Metro-Brix_kitcheb-1043x696.jpg
546 ms
A214_r_MoroccanHabitat_ivory-1043x691.jpg
547 ms
A214_r_MoroccanHabitat_navy-1043x691.jpg
547 ms
A214_r_MoroccanHabitat_patch-1043x610.jpg
580 ms
additional-links-icons-stains.jpg
578 ms
additional-links-icons-water-resistant.jpg
738 ms
additional-link-prevents-bacteria.jpg
738 ms
FPO-tile-buying-guide-signup-block-image.png
513 ms
easy_care.jpg
514 ms
heritage_boy.jpg
512 ms
ad_status.js
322 ms
wAFWjcG1j0S59k6y9gmRkscrkcYt8sjUn-04af-yL2Q.js
207 ms
embed.js
121 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
12 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
38 ms
id
33 ms
Create
105 ms
whytile.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
whytile.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
whytile.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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whytile.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 Whytile.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.
whytile.com
Open Graph data is detected on the main page of Why Tile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: