25.4 sec in total
550 ms
22.2 sec
2.7 sec
Click here to check amazing Fat Dragon content. Otherwise, check out these important facts you probably never knew about fatdragon.com.au
Fat Dragon is open in Mount Lawley. Big flavours and mouth dropping textures. We're old school and loving it! info@fatdragon.com.au
Visit fatdragon.com.auWe analyzed Fatdragon.com.au page load time and found that the first response time was 550 ms and then it took 24.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fatdragon.com.au performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value27.4 s
0/100
25%
Value14.5 s
1/100
10%
Value7,260 ms
0/100
30%
Value0
100/100
15%
Value29.3 s
0/100
10%
550 ms
461 ms
479 ms
487 ms
489 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 11% of them (16 requests) were addressed to the original Fatdragon.com.au, 59% (83 requests) were made to Assets-www.web-dev.euwest1.aws.quandoo.com and 4% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Opentable.com.au.
Page size can be reduced by 20.7 kB (3%)
704.6 kB
684.0 kB
In fact, the total size of Fatdragon.com.au main page is 704.6 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. Only a small number of websites need less resources to load. Javascripts take 539.5 kB which makes up the majority of the site volume.
Potential reduce by 9.6 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 9.6 kB or 67% 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. Fat Dragon images are well optimized though.
Potential reduce by 4.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 1.4 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. Fatdragon.com.au has all CSS files already compressed.
Number of requests can be reduced by 107 (84%)
128
21
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fat Dragon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 102 to 1 for JavaScripts and as a result speed up the page load time.
fatdragon.com.au
550 ms
bootstrap.min.css
461 ms
bootstrap-responsive.css
479 ms
main.css
487 ms
modernizr-2.6.1.min.js
489 ms
qqp2lxn.js
266 ms
index.js
252 ms
loader
20156 ms
jquery.min.js
34 ms
plugins.js
609 ms
main.js
621 ms
br_EN.png
239 ms
desktop_splash_bg.jpg
1160 ms
fat_dragon_logo.png
472 ms
top.png
252 ms
Widget.js
893 ms
bootstrap.js
21 ms
d
108 ms
d
138 ms
collect
112 ms
settings
362 ms
widget
800 ms
gtm.js
350 ms
vendors~main~253ae210.8f38d783.chunk.js
795 ms
vendors~main~0f485567.3e02ca8e.chunk.js
855 ms
vendors~main~033e7a4f.59f475e6.chunk.js
853 ms
vendors~main~fa9d841c.0f73d680.chunk.js
848 ms
vendors~main~cd1be390.5edd2981.chunk.js
909 ms
vendors~main~a05af556.4e1b35f2.chunk.js
1051 ms
vendors~main~7274e1de.36f44896.chunk.js
1048 ms
vendors~main~f9129949.8881781a.chunk.js
1050 ms
vendors~main~7d359b94.d173fea2.chunk.js
1049 ms
vendors~main~4d01349d.5fac6c43.chunk.js
1048 ms
vendors~main~52afbd56.eed69f53.chunk.js
1525 ms
vendors~main~690b702c.cfb256d9.chunk.js
1569 ms
vendors~main~1ceea6da.4a7ea227.chunk.js
1568 ms
vendors~main~9c5b28f6.2065ed2c.chunk.js
1704 ms
vendors~main~b58f7129.8186332c.chunk.js
1703 ms
vendors~main~4548857e.b1d7b84e.chunk.js
1701 ms
vendors~main~678f84af.6ca15edc.chunk.js
1703 ms
vendors~main~f734b0c6.a5c98f79.chunk.js
1701 ms
vendors~main~ab68c3a7.e245ed19.chunk.js
1704 ms
vendors~main~482e28fd.bf43ae01.chunk.js
1737 ms
vendors~main~d1a45290.e3a0673b.chunk.js
1737 ms
vendors~main~2d176a84.b37644f4.chunk.js
1737 ms
vendors~main~52f931a5.3a7f987e.chunk.js
1738 ms
vendors~main~6f7acc4e.4d60e197.chunk.js
1738 ms
vendors~main~1c3a2c3f.f41ed11d.chunk.js
2340 ms
vendors~main~2900d54e.f6a3da02.chunk.js
2344 ms
main~f075b844.018b1391.chunk.js
2344 ms
main~30ccc425.44d197fe.chunk.js
2343 ms
main~2898eb0e.0a6030bc.chunk.js
2348 ms
main~5a11b65b.d372b70f.chunk.js
2330 ms
main~3364b0b4.bf3415cc.chunk.js
2333 ms
main~fe422c04.5e3e91d7.chunk.js
2591 ms
main~c714bc7b.5fddb0c9.chunk.js
2637 ms
main~f4bcfa21.87161857.chunk.js
2636 ms
main~53ca99a6.3453296b.chunk.js
2727 ms
main~39f21978.b825f06a.chunk.js
2723 ms
hotjar-433793.js
1531 ms
Widget
2716 ms
analytics.js
264 ms
bat.js
1680 ms
ytc.js
1073 ms
js
364 ms
js
1033 ms
main~cfcf70d2.ca50fdee.js
1962 ms
linkid.js
614 ms
modules.cf44a0a6b448df1b035e.js
3717 ms
collect
1083 ms
collect
677 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
3693 ms
10074103.json
3025 ms
5795529.js
2965 ms
WidgetLoader
3057 ms
ga-audiences
3055 ms
31.266bcccf.chunk.js
481 ms
476.3f5354de.chunk.js
453 ms
averta-regular.b0b9ebcc.woff
393 ms
averta-bold.f771fbab.woff
366 ms
averta-extrabold.baba6051.woff
392 ms
5795529
229 ms
465.9b17af26.chunk.js
96 ms
466.de385655.chunk.js
55 ms
clarity.js
126 ms
478.b0679e11.chunk.js
141 ms
477.fc632068.chunk.js
149 ms
480.48f0eb4e.chunk.js
146 ms
481.f19ad18d.chunk.js
146 ms
482.22c574aa.chunk.js
146 ms
479.887fb169.chunk.js
139 ms
483.a19e2b38.chunk.js
139 ms
484.b7ababc5.chunk.js
134 ms
467.143c4aa4.chunk.js
132 ms
486.a649a4a8.chunk.js
48 ms
485.ef59c2c2.chunk.js
30 ms
488.2ee3cf45.chunk.js
25 ms
489.98e4ea48.chunk.js
26 ms
490.a45deb08.chunk.js
26 ms
487.7933a681.chunk.js
26 ms
491.6cf024c6.chunk.js
26 ms
492.71543065.chunk.js
44 ms
464.f13e7644.chunk.js
159 ms
20.4dcc126f.chunk.js
136 ms
493.66e678a8.chunk.js
135 ms
vendors~packages-Authentication-components-ForgotPassword-index~packages-Authentication-index~packag~6232dc7a.c2408210.chunk.js
133 ms
vendors~packages-Authentication-components-ForgotPassword-index~packages-Authentication-index~packag~d6dfd2ba.c8ac094b.chunk.js
132 ms
vendors~packages-Detail-index~packages-EditReservation-index~packages-EmbeddedCheckout-Enquiry-index~8a63dd04.9ac73037.chunk.js
131 ms
vendors~QuickActions-Modals~packages-Checkout-components-CheckoutCustomerForm-CountryCodeSelect-inde~621ff7de.355c515d.chunk.js
105 ms
packages-EmbeddedCheckout-index~748942c6.2a4894eb.chunk.js
108 ms
packages-EmbeddedCheckout-index~31ecd969.754d046e.chunk.js
90 ms
packages-EmbeddedCheckout-index~7274e1de.ab55b443.chunk.js
107 ms
packages-EmbeddedCheckout-index~db300d2f.7ab838e3.chunk.js
102 ms
packages-EmbeddedCheckout-index~9c5b28f6.11e106db.chunk.js
105 ms
packages-EmbeddedCheckout-index~2d738248.57703dac.chunk.js
402 ms
packages-EmbeddedCheckout-index~5da819be.4ae8eb70.chunk.js
433 ms
packages-EmbeddedCheckout-index~fe334ae7.593611d2.chunk.js
401 ms
packages-EmbeddedCheckout-index~42cd248f.32f8fb5f.chunk.js
431 ms
packages-EmbeddedCheckout-index~bb9f020d.3ec0cc5a.chunk.js
371 ms
packages-EmbeddedCheckout-index~b59217a9.31bd0888.chunk.js
370 ms
packages-EmbeddedCheckout-index~3d9b8e9e.438ef125.chunk.js
434 ms
packages-EmbeddedCheckout-index~4624fc93.d29484ce.chunk.js
408 ms
packages-EmbeddedCheckout-index~a20da983.c745c742.chunk.js
425 ms
packages-EmbeddedCheckout-index~a2146506.ca084e73.chunk.js
424 ms
509 ms
c.gif
37 ms
chopsticks_red.png
729 ms
phone_icon.png
722 ms
mail_icon.png
723 ms
fb_icon.png
724 ms
chopsticks_white.png
725 ms
d
412 ms
d
450 ms
ga.js
446 ms
load.html
261 ms
d
100 ms
__utm.gif
27 ms
like.php
376 ms
p.gif
85 ms
r2dcYedPhVV.js
140 ms
FEppCFCt76d.png
63 ms
fatdragon.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
Form elements do not have associated labels
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.
fatdragon.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
Page has valid source maps
fatdragon.com.au SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Fatdragon.com.au 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 Fatdragon.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.
fatdragon.com.au
Open Graph data is detected on the main page of Fat Dragon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: