3.1 sec in total
306 ms
2.4 sec
463 ms
Visit goldleafrestaurant.com.au now to see the best up-to-date Gold Leaf Restaurant content and also check out these interesting facts you probably never knew about goldleafrestaurant.com.au
Porto - Responsive HTML5 Template
Visit goldleafrestaurant.com.auWe analyzed Goldleafrestaurant.com.au page load time and found that the first response time was 306 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
goldleafrestaurant.com.au performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value15.6 s
0/100
25%
Value21.3 s
0/100
10%
Value30 ms
100/100
30%
Value0.18
67/100
15%
Value23.3 s
1/100
10%
306 ms
492 ms
27 ms
374 ms
169 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Goldleafrestaurant.com.au, 51% (66 requests) were made to Goldleafrestaurant.com and 27% (35 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (863 ms) relates to the external source Goldleafrestaurant.com.
Page size can be reduced by 1.3 MB (32%)
4.2 MB
2.8 MB
In fact, the total size of Goldleafrestaurant.com.au main page is 4.2 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. 75% 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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 61.8 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 61.8 kB or 87% of the original size.
Potential reduce by 133.0 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. Gold Leaf Restaurant images are well optimized though.
Potential reduce by 789.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 789.6 kB or 73% of the original size.
Potential reduce by 354.1 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. Goldleafrestaurant.com.au needs all CSS files to be minified and compressed as it can save up to 354.1 kB or 86% of the original size.
Number of requests can be reduced by 58 (50%)
117
59
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gold Leaf Restaurant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
goldleafrestaurant.com.au
306 ms
www.goldleafrestaurant.com
492 ms
css
27 ms
bootstrap.css
374 ms
font-awesome.css
169 ms
owl.carousel.css
775 ms
owl.theme.css
127 ms
magnific-popup.css
127 ms
theme.css
255 ms
theme-elements.css
321 ms
theme-blog.css
190 ms
theme-shop.css
222 ms
theme-animate.css
317 ms
settings.css
386 ms
component.css
319 ms
default.css
382 ms
custom.css
384 ms
modernizr.js
384 ms
jquery.js
542 ms
jquery.appear.js
399 ms
jquery.easing.js
400 ms
jquery-cookie.js
400 ms
bootstrap.js
464 ms
common.js
465 ms
jquery.validation.js
525 ms
jquery.stellar.js
526 ms
jquery.easy-pie-chart.js
518 ms
jquery.gmap.js
529 ms
twitter.js
572 ms
jquery.isotope.js
650 ms
owl.carousel.js
656 ms
jflickrfeed.js
592 ms
jquery.magnific-popup.js
647 ms
vide.js
625 ms
theme.js
719 ms
jquery.themepunch.tools.min.js
807 ms
jquery.themepunch.revolution.min.js
863 ms
jquery.flipshow.js
712 ms
js
20 ms
view.home.js
716 ms
view.contact.js
734 ms
custom.js
734 ms
theme.init.js
697 ms
logo.png
288 ms
social-sprites.png
70 ms
slide-bg-full-0.jpg
740 ms
slide-bg-full-1.jpg
406 ms
slide-bg-full-2.jpg
404 ms
slide-bg-full-3.jpg
405 ms
sq1.jpg
285 ms
docklands.jpg
291 ms
sq2.jpg
482 ms
bbq.jpg
402 ms
sq3.jpg
405 ms
burwood.jpg
407 ms
sq4.jpg
481 ms
preston.jpg
429 ms
sq5.jpg
430 ms
springvale.jpg
480 ms
sq6.jpg
483 ms
sunshine.jpg
542 ms
parallax-transparent.jpg
544 ms
logo-footer.png
540 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
167 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
169 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
169 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
169 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
168 ms
fontawesome-webfont.woff
501 ms
common.js
91 ms
map.js
91 ms
util.js
90 ms
geocoder.js
91 ms
marker.js
88 ms
loader.gif
291 ms
timer.png
297 ms
large_left.png
300 ms
large_right.png
335 ms
onion.js
39 ms
openhand_8_8.cur
31 ms
AuthenticationService.Authenticate
149 ms
GeocodeService.Search
180 ms
GeocodeService.Search
146 ms
GeocodeService.Search
181 ms
GeocodeService.Search
148 ms
GeocodeService.Search
146 ms
GeocodeService.Search
223 ms
ViewportInfoService.GetViewportInfo
169 ms
stats.js
17 ms
controls.js
12 ms
transparent.png
30 ms
css
64 ms
google4.png
50 ms
mapcnt6.png
48 ms
sv5.png
48 ms
tmapctrl.png
48 ms
cb_scout5.png
53 ms
imgs8.png
50 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
38 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
38 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
38 ms
pin.png
84 ms
vt
54 ms
vt
38 ms
vt
41 ms
vt
39 ms
vt
39 ms
vt
42 ms
vt
39 ms
vt
42 ms
vt
44 ms
vt
45 ms
vt
47 ms
vt
45 ms
vt
47 ms
vt
66 ms
vt
67 ms
vt
66 ms
vt
69 ms
vt
67 ms
vt
68 ms
vt
84 ms
vt
69 ms
vt
81 ms
vt
84 ms
vt
85 ms
vt
70 ms
infowindow.js
44 ms
goldleafrestaurant.com.au 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
Image elements do not have [alt] attributes
Links do not have a discernible name
goldleafrestaurant.com.au 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
goldleafrestaurant.com.au 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goldleafrestaurant.com.au 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 Goldleafrestaurant.com.au 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.
goldleafrestaurant.com.au
Open Graph description is not detected on the main page of Gold Leaf Restaurant. 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: