3.9 sec in total
643 ms
3 sec
245 ms
Visit fatso.co.nz now to see the best up-to-date Fatso content for New Zealand and also check out these interesting facts you probably never knew about fatso.co.nz
Visit fatso.co.nzWe analyzed Fatso.co.nz page load time and found that the first response time was 643 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fatso.co.nz performance score
name
value
score
weighting
Value14.8 s
0/100
10%
Value25.9 s
0/100
25%
Value25.8 s
0/100
10%
Value9,730 ms
0/100
30%
Value0.408
24/100
15%
Value28.9 s
0/100
10%
643 ms
39 ms
50 ms
43 ms
66 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fatso.co.nz, 75% (47 requests) were made to D1ahfkp8nuejpo.cloudfront.net and 10% (6 requests) were made to Secure.livechatinc.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source D1ahfkp8nuejpo.cloudfront.net.
Page size can be reduced by 991.0 kB (59%)
1.7 MB
683.2 kB
In fact, the total size of Fatso.co.nz main page is 1.7 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. 45% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 19.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. This page needs HTML code to be minified as it can gain 2.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.6 kB or 74% of the original size.
Potential reduce by 36.1 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. Fatso images are well optimized though.
Potential reduce by 723.9 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 723.9 kB or 70% of the original size.
Potential reduce by 211.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. Fatso.co.nz needs all CSS files to be minified and compressed as it can save up to 211.4 kB or 87% of the original size.
Number of requests can be reduced by 21 (37%)
57
36
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fatso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
fatso.co.nz
643 ms
jquery-ui-1.8.19.css
39 ms
screen.css
50 ms
jquery.autocomplete.css
43 ms
jquery.min.js
66 ms
head.0.8.min.js
43 ms
jquery.tools.1.2.6.min.js
36 ms
jquery-ui-1.8.19.min.js
89 ms
jquery.scrollTo-1.4.2-min.js
42 ms
jquery.colorbox-min.js
42 ms
modernizr-1.6.min.js
44 ms
jquery.ba-bbq.1.2.1.min.js
44 ms
jquery-custom-functions.js
44 ms
custom-functions.js
86 ms
canvasloader.min.js
83 ms
cvc-help.js
84 ms
common.min.js
117 ms
livechat.js
84 ms
home_index.js
116 ms
tracking.js
93 ms
ga.js
59 ms
img.png
2173 ms
play-movie-button.png
754 ms
starburst.png
8 ms
510715.jpg
33 ms
510843.jpg
34 ms
509828.jpg
746 ms
510846.jpg
35 ms
510423.jpg
36 ms
509306.jpg
35 ms
510296.jpg
36 ms
510366.jpg
816 ms
510362.jpg
759 ms
510639.jpg
37 ms
510577.jpg
37 ms
510346.jpg
1007 ms
510539.jpg
1496 ms
510078.jpg
1280 ms
510349.jpg
765 ms
Over-32k-Icon.png
770 ms
TV-Icon.png
1297 ms
Bluray_Icon.png
1416 ms
3D-icon.png
1505 ms
smart-icon.png
1282 ms
Plans-icon.png
1286 ms
Movie-Tickets.png
1785 ms
Experiental-icon.png
1818 ms
Facebook-logo.png
1938 ms
twitter.png
1987 ms
facebook.png
1992 ms
__utm.gif
22 ms
script_data.js
176 ms
collect
70 ms
localization.en.0.3632191afe35222a6b78c04d457adc0d_ed689dc6610ed4ed8d97494bd8a2d33e.js
61 ms
ping
102 ms
open_chat.cgi
92 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
71 ms
livechat-modern_7cf45543dc.ttf
30 ms
embedded.20160229123341.js
108 ms
_Incapsula_Resource
30 ms
_Incapsula_Resource
30 ms
wkfQbvfT_02e2IWO3yYueQ.woff
23 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
49 ms
fatso.co.nz 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
Image elements do not have [alt] attributes
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.
fatso.co.nz 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
fatso.co.nz 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 Fatso.co.nz 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 Fatso.co.nz 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.
fatso.co.nz
Open Graph description is not detected on the main page of Fatso. 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: