2.4 sec in total
121 ms
2 sec
315 ms
Click here to check amazing Cafe Tables content. Otherwise, check out these important facts you probably never knew about cafe-tables.com
Welcome to Cafe Tables home page! Make sure to browse our wide variety of table tops and bases! Located and shipped out of Spartanburg, SC.
Visit cafe-tables.comWe analyzed Cafe-tables.com page load time and found that the first response time was 121 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
cafe-tables.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value16.0 s
0/100
25%
Value11.3 s
5/100
10%
Value2,060 ms
7/100
30%
Value0.013
100/100
15%
Value17.0 s
4/100
10%
121 ms
114 ms
307 ms
258 ms
31 ms
Our browser made a total of 166 requests to load all elements on the main page. We found that 81% of them (134 requests) were addressed to the original Cafe-tables.com, 11% (19 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (554 ms) belongs to the original domain Cafe-tables.com.
Page size can be reduced by 169.4 kB (10%)
1.7 MB
1.5 MB
In fact, the total size of Cafe-tables.com main page is 1.7 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 158.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 158.9 kB or 80% of the original size.
Potential reduce by 1.1 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. Cafe Tables images are well optimized though.
Potential reduce by 9.4 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 0 B
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. Cafe-tables.com has all CSS files already compressed.
Number of requests can be reduced by 115 (83%)
139
24
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cafe Tables. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 116 to 1 for JavaScripts and as a result speed up the page load time.
cafe-tables.com
121 ms
www.cafe-tables.com
114 ms
www.cafe-tables.com
307 ms
wp-polyfill-inert.min.js
258 ms
regenerator-runtime.min.js
31 ms
wp-polyfill.min.js
31 ms
hooks.min.js
258 ms
w.js
50 ms
jquery.min.js
41 ms
jquery-migrate.min.js
51 ms
underscore.min.js
57 ms
wp-util.min.js
55 ms
jquery.blockUI.min.js
55 ms
rbtools.min.js
57 ms
rs6.min.js
124 ms
add-to-cart.min.js
79 ms
js.cookie.min.js
118 ms
woocommerce.min.js
118 ms
woocommerce-add-to-cart-2568132a0db570d89f579e8e167058c1.js
152 ms
swap.js
118 ms
polyfill.js
55 ms
js
123 ms
js
151 ms
swap.js
117 ms
rbtools.min.js
151 ms
rs6.min.js
392 ms
accounting.min.js
135 ms
add-to-cart-variation.min.js
173 ms
addons.min.js
176 ms
script.min.js
136 ms
sourcebuster.min.js
172 ms
order-attribution.min.js
176 ms
react.min.js
176 ms
deprecated.min.js
177 ms
dom.min.js
178 ms
react-dom.min.js
179 ms
escape-html.min.js
180 ms
element.min.js
237 ms
is-shallow-equal.min.js
236 ms
i18n.min.js
201 ms
keycodes.min.js
235 ms
priority-queue.min.js
237 ms
compose.min.js
239 ms
private-apis.min.js
238 ms
js
131 ms
redux-routine.min.js
233 ms
data.min.js
434 ms
lodash.min.js
240 ms
wc-blocks-registry-279ae6456d2dd9ec4adc04603433ced4.js
220 ms
url.min.js
219 ms
api-fetch.min.js
213 ms
wc-settings-a55b194b3d90b03073d374cce019bceb.js
236 ms
data-controls.min.js
236 ms
html-entities.min.js
218 ms
gtm.js
110 ms
notices.min.js
176 ms
wc-blocks-middleware-c82e19b2d9701e00153ffe471cf06a7f.js
191 ms
css
78 ms
513cd87c8a8b872730992b45440cbe33.css
554 ms
wc-blocks-data-df5f4cb7060bde28744dbb4f8b2a1279.js
201 ms
dom-ready.min.js
157 ms
a11y.min.js
173 ms
primitives.min.js
173 ms
81 ms
warning.min.js
147 ms
blocks-components-8fc0d4a23f15f5f912855b3c9d1e1ccc.js
143 ms
blocks-checkout-4010cf9209fc359e236c4d4db4c7419b.js
143 ms
order-attribution-blocks.min.js
159 ms
swatches-and-photos-d83cc930e41dde12d8be457fef7e592b.js
194 ms
jquery.payment.min.js
159 ms
sv-wc-payment-gateway-payment-form-3f9483a549df38b6f86513bb8895b83a.js
193 ms
wc-authorize-net-cim.min.js
193 ms
core.min.js
191 ms
tabs.min.js
189 ms
pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf
40 ms
pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf
50 ms
pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf
65 ms
pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf
69 ms
pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf
78 ms
pxiEyp8kv8JHgFVrJJnedw.ttf
81 ms
pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf
78 ms
pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf
78 ms
pxiGyp8kv8JHgFVrLPTufntF.ttf
78 ms
accordion.min.js
179 ms
datepicker.min.js
155 ms
mediaelement-and-player.min.js
155 ms
mediaelement-migrate.min.js
155 ms
wp-mediaelement.min.js
156 ms
jquery.appear-3fbaf4449e525ed7778a3d73b98d81e2.js
155 ms
modernizr.custom.85257-c5825fc35343bb172a752e1da47e8289.js
156 ms
hoverIntent.min.js
155 ms
jquery.plugin-ded875e1d410b36f00908c33241eabe5.js
155 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
48 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
61 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
63 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
63 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf
64 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
64 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
65 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
65 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
69 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
65 ms
jquery.countdown.min.js
150 ms
71 ms
owl.carousel.min.js
149 ms
parallax.min.js
264 ms
select2.full.min.js
148 ms
easypiechart-caa190f804b00ce668830f1f3cd9de03.js
148 ms
jquery.waypoints.min.js
136 ms
Chart.min.js
136 ms
counter-ec8ea870a0289706ec84958676770e8b.js
135 ms
absoluteCounter-f1a7cdfd510813dd713e71d7730c93c2.js
144 ms
fluidvids.min.js
132 ms
jquery.prettyPhoto.min.js
127 ms
jquery.nicescroll.min.js
124 ms
ScrollToPlugin.min.js
122 ms
TweenLite.min.js
125 ms
TimelineLite.min.js
121 ms
CSSPlugin.min.js
121 ms
EasePack.min.js
194 ms
g.gif
45 ms
jquery.mixitup.min.js
165 ms
jquery.multiscroll.min.js
165 ms
jquery.waitforimages-abac0bcf62682e52b4e823aeb17bb8c7.js
377 ms
jquery.infinitescroll.min.js
164 ms
jquery.easing.1.3-7b7ce8aaa6d66e7600ba61ad357a0027.js
165 ms
skrollr-34339425dfe22662ecb9475ab5c6045c.js
164 ms
slick.min.js
148 ms
bootstrapCarousel-94d22428ccc6a5caa435d0d1af22b2c0.js
150 ms
jquery.touchSwipe.min.js
147 ms
jquery.flexslider.min.js
148 ms
isotope.pkgd.min.js
147 ms
packery-mode.pkgd.min.js
147 ms
smoothPageScroll-2e31ad1c69dfa05f858226434f842564.js
364 ms
modules.min.js
147 ms
js_composer_front.min.js
146 ms
like-9e64735accf6c9c91d0a54dd67371462.js
147 ms
new-tab-4a474dbe8f02435c250a3dad93680176.js
146 ms
pum-site-scripts-0b9f13153ea394aa75e208abc6e5fefd.js
147 ms
child-scripts-36308d2e283df251ffd3660859a52e72.js
145 ms
tvc-ee-google-analytics-7be33bd6b84f0a65f1d7d45bc714f3ca.js
145 ms
lazyload.min.js
145 ms
ElegantIcons.woff
136 ms
Simple-Line-Icons.ttf
135 ms
dummy.png
154 ms
newweld.jpg
146 ms
arrow.png
146 ms
ct-logo-1.png
12 ms
logo-2.png
10 ms
201269_277338052383864_1834452944_o-250x250.jpg
373 ms
residentialnew-250x250.jpg
28 ms
IMG_3182-250x250.jpg
18 ms
Still-charcuterie-3-850x450.jpg
29 ms
BBHP1500DH-304x378.jpg
44 ms
Bistro-4-304x378.png
45 ms
1018-compilation_2-304x378.jpg
46 ms
Carrara-White-sq-2-304x378.jpg
56 ms
Plank-Walnut-2-304x378.jpg
56 ms
www.cafe-tables.com
373 ms
facebookicon.png
65 ms
instaicon.png
74 ms
css
84 ms
sbi-sprite.png
200 ms
fontawesome-webfont.woff
274 ms
fontawesome-webfont.woff
327 ms
Linearicons-Free.woff
292 ms
cafe-tables.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
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.
cafe-tables.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
cafe-tables.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
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 Cafe-tables.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 Cafe-tables.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.
cafe-tables.com
Open Graph data is detected on the main page of Cafe Tables. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: