1.2 sec in total
108 ms
921 ms
162 ms
Visit fanshop.com.au now to see the best up-to-date Fan Shop content and also check out these interesting facts you probably never knew about fanshop.com.au
The Fan Shop - Your Fan and Lighting Specialists in Indoor Ceiling Fans, Outdoor Ceiling Fans, Ceiling Fans With Light, Ceiling Fans With Remote Control & More
Visit fanshop.com.auWe analyzed Fanshop.com.au page load time and found that the first response time was 108 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
fanshop.com.au performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value9.0 s
1/100
25%
Value15.5 s
0/100
10%
Value8,610 ms
0/100
30%
Value0.021
100/100
15%
Value27.1 s
0/100
10%
108 ms
87 ms
103 ms
56 ms
65 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Fanshop.com.au, 78% (31 requests) were made to Static.parastorage.com and 10% (4 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (626 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.2 MB (77%)
2.9 MB
645.6 kB
In fact, the total size of Fanshop.com.au main page is 2.9 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. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 51.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 51.6 kB or 82% of the original size.
Potential reduce by 2.1 MB
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 2.1 MB or 77% of the original size.
Potential reduce by 44.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. Fanshop.com.au needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 84% of the original size.
Number of requests can be reduced by 28 (74%)
38
10
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fan Shop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
fanshop.com.au
108 ms
www.fanshop.com.au
87 ms
bt
103 ms
require.min.js
56 ms
main-r.min.js
65 ms
viewer.css
93 ms
UpgradeBrowser.js
95 ms
dynamicmodel
46 ms
1e3f31_6e448ad848e3354cab1015eb966d5c33_422.json.z
284 ms
1e3f31_4efcd330c6896135f6f5bc830b30ec09_421.json.z
626 ms
ugc-viewer
45 ms
bt
103 ms
skins.min.js
235 ms
components.min.js
230 ms
utils.min.js
69 ms
core.min.js
77 ms
react-with-addons.min.js
69 ms
lodash.min.js
30 ms
TweenMax.min.js
67 ms
layout.min.js
228 ms
tpa.min.js
233 ms
fonts.min.js
227 ms
animations.min.js
230 ms
swfobject.min.js
231 ms
mousetrap.min.js
233 ms
tweenEngine.min.js
232 ms
DrawSVGPlugin.min.js
234 ms
react-dom.min.js
232 ms
ScrollToPlugin.min.js
235 ms
widgets.min.js
232 ms
experiment.js
234 ms
render.min.js
234 ms
wixappsCore.min.js
239 ms
wixappsClassics.min.js
238 ms
wixappsBuilder.min.js
234 ms
zepto.min.js
232 ms
color.min.js
233 ms
latin.css
332 ms
react-dom-server.min.js
302 ms
bt
144 ms
fanshop.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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
fanshop.com.au 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
Page has valid source maps
fanshop.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
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
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanshop.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 Fanshop.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.
fanshop.com.au
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: