33.6 sec in total
4.6 sec
28 sec
1 sec
Visit floof.sg now to see the best up-to-date FLooF content and also check out these interesting facts you probably never knew about floof.sg
Visit floof.sgWe analyzed Floof.sg page load time and found that the first response time was 4.6 sec and then it took 29 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
floof.sg performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value48.8 s
0/100
25%
Value37.1 s
0/100
10%
Value1,360 ms
17/100
30%
Value0.409
24/100
15%
Value30.9 s
0/100
10%
4626 ms
1525 ms
756 ms
1748 ms
772 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 88% of them (90 requests) were addressed to the original Floof.sg, 3% (3 requests) were made to Cdnjs.cloudflare.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (10.1 sec) belongs to the original domain Floof.sg.
Page size can be reduced by 1.5 MB (19%)
8.2 MB
6.6 MB
In fact, the total size of Floof.sg main page is 8.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. 60% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.
Potential reduce by 139.7 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 139.7 kB or 82% of the original size.
Potential reduce by 33.4 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. FLooF images are well optimized though.
Potential reduce by 583.2 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 583.2 kB or 75% of the original size.
Potential reduce by 789.7 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. Floof.sg needs all CSS files to be minified and compressed as it can save up to 789.7 kB or 87% of the original size.
Number of requests can be reduced by 64 (67%)
96
32
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLooF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
floof.sg
4626 ms
style.min.css
1525 ms
jquery.bxslider.css
756 ms
9797-layout.css
1748 ms
followups.css
772 ms
woocommerce-layout.css
1024 ms
woocommerce.css
2005 ms
modal.css
1516 ms
frontend.css
1524 ms
style.css
2015 ms
98ab316a49013f7d00c299cd82322e7b-layout-bundle.css
2803 ms
jquery-ui.min.css
35 ms
frontend.css
2285 ms
frontend.css
2296 ms
wcs-att-frontend.css
2498 ms
wc-memberships-frontend.min.css
2773 ms
style.css
2784 ms
jquery.magnificpopup.min.css
3050 ms
bootstrap-4.min.css
4086 ms
skin-6507afd1655ab.css
4052 ms
style.css
3533 ms
animate.min.css
4063 ms
css
44 ms
jquery.min.js
4081 ms
jquery-migrate.min.js
3799 ms
giftup-cart.js
4297 ms
fue-account-subscriptions.js
4580 ms
underscore.min.js
5062 ms
wp-util.min.js
4810 ms
jquery.blockUI.min.js
4835 ms
add-to-cart-variation.min.js
4837 ms
add-to-cart.min.js
5042 ms
js.cookie.min.js
5321 ms
woocommerce.min.js
5582 ms
gtm4wp-woocommerce-enhanced.js
5819 ms
4e7a9c8bc8.js
54 ms
jquery.bind-first-0.2.3.min.js
5608 ms
js.cookie-2.1.3.min.js
5808 ms
public.js
6578 ms
all.min.css
38 ms
omise-payment-credit-card.js
5332 ms
omise-download-promptpay-as-png.js
5600 ms
googlepay-button-index.umd.min.js
5596 ms
omise-payment-atome.js
5538 ms
jquery.waypoints.min.js
5445 ms
jquery.imagesloaded.min.js
5350 ms
isotope.pkgd.min.js
5944 ms
jquery.easing.min.js
5468 ms
jquery.fitvids.min.js
5317 ms
jquery.bxslider.min.js
5570 ms
jquery-carousel.js
5701 ms
9797-layout.js
6061 ms
fue-front.js
5499 ms
modal.js
5336 ms
frontend.js
5675 ms
jquery.ba-throttle-debounce.min.js
5528 ms
d3227a82aace42573fe27752ff9caaed-layout-bundle.js
6182 ms
scripts.js
5225 ms
jquery.magnificpopup.min.js
5317 ms
bootstrap-4.min.js
5542 ms
theme.min.js
5291 ms
fbevents.js
141 ms
gtm.js
220 ms
logo-floof.png
2595 ms
White-Fish-in-Bowl.jpg
6866 ms
hero-image-02-1.png
5138 ms
is-it-dinnertime-yet.png
4145 ms
is-this-hightech.png
4892 ms
floof-brew-bottle.png
5296 ms
icon-nutritionally-balanced.png
3745 ms
icon-single-protein-formulas.png
4508 ms
icon-100-human-grade.png
4898 ms
icon-avs-licensed-final.png
5294 ms
icon-no-nonsense-final.png
5645 ms
icon-pasteurised-products-final.png
5657 ms
500g-Salmon-Pack-Thumbnail-Edited-400x400.jpeg
6431 ms
Beef-sausages-Cover-400x400.jpg
6549 ms
Floof-Beer-Product-Image-400x400.jpeg
6319 ms
Kangaroo-Steak-web-min-400x400.jpg
6651 ms
Filmstrip-1.png
7913 ms
page-1-e1665753178503.png
10134 ms
page-2-e1665753285842.png
9429 ms
font
85 ms
fa-solid-900.ttf
82 ms
fa-regular-400.ttf
83 ms
Nunito-Regular.ttf
7726 ms
js
86 ms
destination
60 ms
track.js
55 ms
Ultimate-Icons.ttf
7654 ms
habbly_-webfont.woff
7330 ms
Janice-Alfie-2-scaled-e1660892689316.jpeg
8656 ms
Joycelyn-Kobi-Charcoal-e1660892717158.jpg
8785 ms
Joanne-Belle-1-scaled-e1660892471780.jpg
8241 ms
Mai-Bheem1-scaled-e1668790096325.jpeg
7873 ms
Sharon-Leah-2-scaled-e1668790030161.jpg
9070 ms
fresh-commercial-thumb.png
9254 ms
why-kanggaroo-thumb.png
9145 ms
differences-th.png
9567 ms
footer-logo.png
8540 ms
payment-gateway-15-e1668582925667.png
8765 ms
woocommerce-smallscreen.css
763 ms
floof.sg 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
floof.sg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
floof.sg 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floof.sg 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 Floof.sg 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.
floof.sg
Open Graph description is not detected on the main page of FLooF. 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: