12.8 sec in total
514 ms
11.2 sec
1 sec
Click here to check amazing Tokara content for South Africa. Otherwise, check out these important facts you probably never knew about tokara.com
We make wine that moves mountains And no matter where you find yourselves on this great globe, when you taste our wine, it will bring those mountains to you. WINE...
Visit tokara.comWe analyzed Tokara.com page load time and found that the first response time was 514 ms and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tokara.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value20.8 s
0/100
25%
Value20.0 s
0/100
10%
Value4,830 ms
0/100
30%
Value0.033
100/100
15%
Value38.0 s
0/100
10%
514 ms
2273 ms
967 ms
738 ms
740 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 82% of them (120 requests) were addressed to the original Tokara.com, 8% (12 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Cdn.commerce7.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Tokara.com.
Page size can be reduced by 476.1 kB (7%)
7.0 MB
6.5 MB
In fact, the total size of Tokara.com main page is 7.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. 70% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 438.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 438.9 kB or 48% of the original size.
Potential reduce by 17.9 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. Tokara images are well optimized though.
Potential reduce by 7.8 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 11.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. Tokara.com has all CSS files already compressed.
Number of requests can be reduced by 110 (86%)
128
18
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokara. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 47 to 1 for CSS and as a result speed up the page load time.
tokara.com
514 ms
www.tokara.com
2273 ms
frontend-lite.min.css
967 ms
general.min.css
738 ms
eael-6687.css
740 ms
post-6687.css
762 ms
eael-6705.css
766 ms
post-6705.css
986 ms
blocks.style.build.css
993 ms
styles.css
1013 ms
cookie-law-info-public.css
1014 ms
cookie-law-info-gdpr.css
1204 ms
embedpress.css
1224 ms
commerce7-for-wordpress.css
1227 ms
commerce7.css
27 ms
font-awesome.min.css
1229 ms
style.css
1263 ms
grid-system.css
1265 ms
style.css
1686 ms
header-secondary-nav.css
1467 ms
header-perma-transparent.css
1466 ms
responsive.css
1473 ms
skin-original.css
1514 ms
menu-dynamic.css
1516 ms
ekiticons.css
1710 ms
eael-8875.css
1717 ms
elementor-icons.min.css
1719 ms
swiper.min.css
1766 ms
post-6523.css
1766 ms
embedpress-elementor.css
1924 ms
frontend-lite.min.css
1952 ms
post-8875.css
1956 ms
dashicons.min.css
2208 ms
plyr.css
2017 ms
salient-dynamic-styles.css
2275 ms
style.css
2162 ms
widget-styles.css
2443 ms
responsive.css
2208 ms
css
45 ms
css
66 ms
dineplan.widget.min.js
297 ms
dineplan.widget.min.js
25 ms
fontawesome.min.css
1543 ms
brands.min.css
1671 ms
solid.min.css
1716 ms
widget-icon-list.min.css
1715 ms
jquery.min.js
1819 ms
commerce7.js
13 ms
api.js
39 ms
cookie-law-info-table.css
1553 ms
magnific.css
1658 ms
core.css
1701 ms
animations.min.css
1694 ms
jquery-migrate.min.js
1693 ms
cookie-law-info-public.js
1593 ms
plyr.polyfilled.js
1669 ms
general.min.js
2062 ms
eael-6687.js
2056 ms
wp-polyfill-inert.min.js
2030 ms
regenerator-runtime.min.js
1827 ms
wp-polyfill.min.js
1818 ms
hooks.min.js
2111 ms
i18n.min.js
2070 ms
index.js
2072 ms
index.js
1885 ms
pdfobject.min.js
1872 ms
initplyr.js
1864 ms
front.js
2038 ms
vimeo-player.js
1998 ms
react.min.js
2001 ms
deprecated.min.js
1843 ms
dom.min.js
1827 ms
react-dom.min.js
2076 ms
escape-html.min.js
1978 ms
element.min.js
1842 ms
is-shallow-equal.min.js
1799 ms
keycodes.min.js
1799 ms
priority-queue.min.js
1757 ms
compose.min.js
1956 ms
private-apis.min.js
1845 ms
redux-routine.min.js
1783 ms
data.min.js
1764 ms
ads.js
1791 ms
documents-viewer-script.js
1760 ms
jquery.easing.min.js
1835 ms
jquery.mousewheel.min.js
1805 ms
priority.js
1800 ms
transit.min.js
1802 ms
waypoints.js
1746 ms
imagesLoaded.min.js
1749 ms
gtm.js
415 ms
hoverintent.min.js
1450 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ArQbMZhKQ.woff
45 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKQ.woff
45 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKQ.woff
117 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_LjQbMZhKQ.woff
182 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjRbMZhKQ.woff
184 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKQ.woff
183 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKQ.woff
183 ms
co3bmX5slCNuHLi8bLeY9MK7whWMhyjYqXtM.woff
183 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQWlhfvg-O.woff
227 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQAllfvg-O.woff
227 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQdl9fvg-O.woff
227 ms
co3YmX5slCNuHLi8bLeY9MK7whWMhyjQEl5fvg-O.woff
227 ms
magnific.js
1455 ms
anime.min.js
1460 ms
superfish.js
1459 ms
init.js
2008 ms
touchswipe.min.js
1496 ms
frontend-script.js
1657 ms
widget-scripts.js
1646 ms
wpcf7-recaptcha-controls.js
1409 ms
webpack-pro.runtime.min.js
1468 ms
webpack.runtime.min.js
1622 ms
frontend-modules.min.js
1652 ms
frontend.min.js
1484 ms
waypoints.min.js
1578 ms
core.min.js
1683 ms
frontend.min.js
1704 ms
elements-handlers.min.js
1706 ms
animate-circle.min.js
1487 ms
elementor.js
1548 ms
fa-brands-400.woff
1802 ms
elementskit.woff
2409 ms
admin-ajax.php
2247 ms
Tokara-Logo-1.0-3.png
1690 ms
Tokara-Crest-Favicon.png
1490 ms
WebsiteHome2Landscape-1-e1669634330376.jpg
2315 ms
Tokara-Landscape-April-2018-003.jpg
3198 ms
Tokara-Range.jpg
1721 ms
Tokara-CabSauv-2021web.jpg
1781 ms
RC-CabSauv-2020web.jpg
1935 ms
Directors-Reserve-Red-2020wh-1024x1024.jpg
1838 ms
telos-packshot-on-white-1659017971794.jpeg
1984 ms
DJI_0896-HDR.jpg
3235 ms
DJI_0896-HDR-633x1024.jpg
2321 ms
top-view-vineyard-TOKARA.jpg
2371 ms
Tokara-Premium-Olive-Oil-006.jpg
2175 ms
Artboard-%E2%80%93-1-1024x649.png
2100 ms
Tokara-Logo-1.0-3.svg
2227 ms
recaptcha__en.js
30 ms
fonts.css
180 ms
jquery.min.js
42 ms
manifest.8173c941c2904511085c.js.gz
8 ms
vendor.b63dcd6c7ab46cfc7b54.js.gz
47 ms
bundle.80226a78be6c330364a3.js.gz
36 ms
tokara.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
Links do not have a discernible name
tokara.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
Browser errors were logged to the console
Page has valid source maps
tokara.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
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokara.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 Tokara.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.
tokara.com
Open Graph data is detected on the main page of Tokara. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: