11.1 sec in total
1.3 sec
9.6 sec
147 ms
Visit courtclassique.co.za now to see the best up-to-date Court Classique content and also check out these interesting facts you probably never knew about courtclassique.co.za
Nestling in upmarket diplomatic suburb of Arcadia, Pretoria, the Court Classique Suite hotel offers easy access to the major Gauteng business centres ...
Visit courtclassique.co.zaWe analyzed Courtclassique.co.za page load time and found that the first response time was 1.3 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
courtclassique.co.za performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value20.3 s
0/100
25%
Value22.3 s
0/100
10%
Value100 ms
98/100
30%
Value0.203
61/100
15%
Value16.0 s
6/100
10%
1320 ms
199 ms
37 ms
209 ms
301 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 60% of them (58 requests) were addressed to the original Courtclassique.co.za, 17% (16 requests) were made to In1media.s3.amazonaws.com and 4% (4 requests) were made to Search.bookin1.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Courtclassique.co.za.
Page size can be reduced by 229.8 kB (31%)
744.7 kB
514.9 kB
In fact, the total size of Courtclassique.co.za main page is 744.7 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. 50% of websites need less resources to load. Images take 592.2 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.3 kB or 78% of the original size.
Potential reduce by 126.5 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. Obviously, Court Classique needs image optimization as it can save up to 126.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 38.1 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 38.1 kB or 53% of the original size.
Potential reduce by 35.9 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. Courtclassique.co.za needs all CSS files to be minified and compressed as it can save up to 35.9 kB or 82% of the original size.
Number of requests can be reduced by 40 (43%)
93
53
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Court Classique. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
courtclassique.co.za
1320 ms
grid_24.css
199 ms
jsapi
37 ms
date.js
209 ms
jquery.ui.datepicker.js
301 ms
searchBox-utils-min.js
214 ms
stmenu.js
1049 ms
style2.css
532 ms
ui.all.css
424 ms
jquery.js
68 ms
jquery-ui.min.js
100 ms
jquery.min.js
46 ms
fadeslideshow.js
1882 ms
menu2a.js
808 ms
mouseover.js
283 ms
wejs
141 ms
jquery.ui.base.css
113 ms
jquery.ui.theme.css
304 ms
jquery.ui.core.css
333 ms
jquery.ui.resizable.css
309 ms
jquery.ui.selectable.css
341 ms
jquery.ui.accordion.css
360 ms
jquery.ui.autocomplete.css
361 ms
jquery.ui.button.css
374 ms
jquery.ui.dialog.css
421 ms
jquery.ui.slider.css
446 ms
jquery.ui.tabs.css
448 ms
jquery.ui.datepicker.css
463 ms
jquery.ui.progressbar.css
465 ms
ui.button.css
485 ms
tripadvisor_logo_115x18.gif
66 ms
index_08.jpg
4523 ms
index_08b.jpg
1105 ms
index_08c.jpg
565 ms
booo.jpg
567 ms
03f.jpg
577 ms
02f.jpg
1060 ms
01f.jpg
856 ms
04f.jpg
850 ms
frr.jpg
857 ms
stip.jpg
1383 ms
onder2.jpg
1408 ms
onder4.jpg
2455 ms
HomeS.jpg
1339 ms
facebook-icon1.png
2933 ms
twitter_new.png
1622 ms
102d.jpg
1670 ms
all.js
15 ms
f5.jpg
2198 ms
stdom.js
1891 ms
stinit.js
1925 ms
blank.gif
2157 ms
menu6_01.jpg
2195 ms
menu7_01.jpg
2438 ms
menu6_02.jpg
2469 ms
menu7_02.jpg
2469 ms
arrow_r.gif
2708 ms
menu6_03.jpg
2707 ms
menu7_03.jpg
2738 ms
menu6_04.jpg
3710 ms
menu7_04.jpg
2978 ms
menu6_05.jpg
2994 ms
menu7_05.jpg
3011 ms
menu6_06.jpg
3191 ms
menu7_06.jpg
4350 ms
menu6_07.jpg
3270 ms
menu7_07.jpg
3278 ms
menu6_08.jpg
3726 ms
37 ms
xd_arbiter.php
20 ms
xd_arbiter.php
30 ms
menu7_08.jpg
4500 ms
index_07a.jpg
3033 ms
index_14c.jpg
3132 ms
WidgetEmbed-excellent
97 ms
cdswidEXC-v22775008216a.css%20%27%29%3B
1 ms
cdswidgets_min-c-v23892882724a.js
36 ms
cdswidEXC-v22775008216a.css
35 ms
index_102b-over.jpg
2183 ms
index_102c-over.jpg
2728 ms
ga.js
18 ms
ui-bg_flat_50_ffffff_40x100.png
104 ms
loading.gif
2505 ms
__utm.gif
82 ms
transparent_pixel-11863-2.gif
10 ms
tripadvisor_logo_115x18.gif
8 ms
index2_11-over.jpg
292 ms
index2_12-over.jpg
301 ms
index2_13-over.jpg
293 ms
index2_14-over.jpg
1234 ms
index2_15-over.jpg
296 ms
index2_16-over.jpg
293 ms
index2_17-over.jpg
1564 ms
index2_18-over.jpg
563 ms
index2_19-over.jpg
562 ms
index2_20-over.jpg
1567 ms
courtclassique.co.za 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.
courtclassique.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
courtclassique.co.za 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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Courtclassique.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Courtclassique.co.za main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
courtclassique.co.za
Open Graph description is not detected on the main page of Court Classique. 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: