5.8 sec in total
1 sec
4.6 sec
189 ms
Click here to check amazing Tokara content for South Africa. Otherwise, check out these important facts you probably never knew about tokara.com
Visit tokara.comWe analyzed Tokara.com page load time and found that the first response time was 1 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tokara.com performance score
name
value
score
weighting
Value13.0 s
0/100
10%
Value19.2 s
0/100
25%
Value52.2 s
0/100
10%
Value86,490 ms
0/100
30%
Value0.035
100/100
15%
Value118.8 s
0/100
10%
1001 ms
521 ms
518 ms
536 ms
985 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tokara.com, 95% (42 requests) were made to Tokara.co.za and 2% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Tokara.co.za.
Page size can be reduced by 225.8 kB (56%)
403.2 kB
177.3 kB
In fact, the total size of Tokara.com main page is 403.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 256.6 kB which makes up the majority of the site volume.
Potential reduce by 13.3 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 13.3 kB or 80% of the original size.
Potential reduce by 5.3 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 177.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 177.6 kB or 69% of the original size.
Potential reduce by 29.6 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 needs all CSS files to be minified and compressed as it can save up to 29.6 kB or 79% of the original size.
Number of requests can be reduced by 11 (26%)
43
32
The browser has sent 43 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 12 to 1 for JavaScripts and as a result speed up the page load time.
tokara.com
1001 ms
style.css
521 ms
styles.css
518 ms
pagenavi-css.css
536 ms
jquery.js
985 ms
jquery.main.js
533 ms
menu.js
743 ms
gallery.js
744 ms
functions.js
762 ms
CSSPlugin.js
1007 ms
EasePack.js
968 ms
TweenLite.js
972 ms
jquery.form.js
1005 ms
scripts.js
1195 ms
comment-reply.js
1195 ms
bg-html.jpg
679 ms
ga.js
16 ms
bg-body.jpg
1351 ms
bg-wrapper.png
232 ms
bg-header.gif
401 ms
logo.jpg
400 ms
bg-nav.gif
421 ms
bg-nav-hover.gif
462 ms
separators.gif
510 ms
1-TOKARA_winery_Stellenbosch-960x499.jpg
1720 ms
2-Vineyards-e1324379506415.jpg
1725 ms
3-Wine_in_the_vineyards-e1324379484338.jpg
1320 ms
8-Outside_view_of_the_Delicatessen-e1324379421911.jpg
1593 ms
7-Inside_features-e1324379541203.jpg
1652 ms
6-Tokara_wines-e1324379457177.jpg
1774 ms
4-Olives-e1324379470633.jpg
2250 ms
1-View_of_the_restaurant-e1324379527572.jpg
2498 ms
bg-switcher.png
1884 ms
bg-switcher-item.png
1942 ms
img06.png
2387 ms
img07.png
2003 ms
img08.png
2118 ms
img09.png
2165 ms
img10.jpg
2231 ms
bg-link-prev.png
2350 ms
bg-link-next.png
2389 ms
bg-footer.gif
2460 ms
icons.gif
2478 ms
bg-sub-nav.png
2391 ms
tokara.com accessibility score
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
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
[id] attributes on active, focusable elements are not unique
tokara.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
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
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 description is not detected on the main page of Tokara. 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: