Tools & Wizards About Us
floata.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

floata.com

www.Floata.com

Page Load Speed

20.8 sec in total

First Response

1.5 sec

Resources Loaded

15.3 sec

Page Rendered

4 sec

floata.com screenshot

About Website

Click here to check amazing Floata content for Canada. Otherwise, check out these important facts you probably never knew about floata.com

Visit floata.com

Key Findings

We analyzed Floata.com page load time and found that the first response time was 1.5 sec and then it took 19.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

floata.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value25.8 s

0/100

25%

SI (Speed Index)

Value9.0 s

15/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.186

66/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

floata.com

1546 ms

wp-emoji-release.min.js

801 ms

shortcodes.css

1638 ms

linecons.css

2238 ms

font-awesome.min.css

587 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 94% of them (64 requests) were addressed to the original Floata.com, 3% (2 requests) were made to Youtube.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.4 sec) belongs to the original domain Floata.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (21%)

Content Size

9.6 MB

After Optimization

7.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Floata.com main page is 9.6 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. 55% of websites need less resources to load. Images take 7.4 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 40.7 kB

  • Original 53.8 kB
  • After minification 52.8 kB
  • After compression 13.1 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 40.7 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 201.7 kB

  • Original 7.4 MB
  • After minification 7.2 MB

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. Floata images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 645.1 kB

  • Original 898.9 kB
  • After minification 839.1 kB
  • After compression 253.8 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 645.1 kB or 72% of the original size.

CSS Optimization

-90%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 122.3 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. Floata.com needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (77%)

Requests Now

65

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floata. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

floata.com

floata.com

1546 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

801 ms

shortcodes.css

shortcodes.css

1638 ms

linecons.css

linecons.css

2238 ms

font-awesome.min.css

font-awesome.min.css

587 ms

steadysets.css

steadysets.css

591 ms

mediaelementplayer.css

mediaelementplayer.css

193 ms

pixelicons.css

pixelicons.css

302 ms

advanced-responsive-video-embedder-public.css

advanced-responsive-video-embedder-public.css

708 ms

styles.css

styles.css

692 ms

settings.css

settings.css

1500 ms

js_composer.css

js_composer.css

2037 ms

style.css

style.css

1691 ms

icomoon.css

icomoon.css

897 ms

mobius-grid.css

mobius-grid.css

1145 ms

jquery-ui.min.css

jquery-ui.min.css

1331 ms

css

css

73 ms

post-like.css

post-like.css

1453 ms

modernizr.js

modernizr.js

1585 ms

jquery.js

jquery.js

3252 ms

jquery-migrate.min.js

jquery-migrate.min.js

1670 ms

youtube.js

youtube.js

1725 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

2454 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

2378 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

2534 ms

jquery.easing.js

jquery.easing.js

2137 ms

owl.carousel.js

owl.carousel.js

2237 ms

easypiechart.js

easypiechart.js

2241 ms

jquery.appear.js

jquery.appear.js

2267 ms

themeone-shortcodes.js

themeone-shortcodes.js

2646 ms

post-like.js

post-like.js

2382 ms

jquery.form.min.js

jquery.form.min.js

2429 ms

scripts.js

scripts.js

2500 ms

js_composer_front.js

js_composer_front.js

2502 ms

smoothscroll.js

smoothscroll.js

2537 ms

history.js

history.js

2612 ms

ajaxify.js

ajaxify.js

2619 ms

owl.carousel.js

owl.carousel.js

2728 ms

hammer.js

hammer.js

2551 ms

isotope.js

isotope.js

2746 ms

sly.js

sly.js

2225 ms

custom.js

custom.js

3770 ms

comment-reply.min.js

comment-reply.min.js

2142 ms

mobius-grid.js

mobius-grid.js

2208 ms

core.min.js

core.min.js

2127 ms

datepicker.min.js

datepicker.min.js

2111 ms

widget.min.js

widget.min.js

1851 ms

button.min.js

button.min.js

1668 ms

spinner.min.js

spinner.min.js

1635 ms

wp-embed.min.js

wp-embed.min.js

1603 ms

iframe_api

iframe_api

378 ms

floata.png

floata.png

541 ms

crab.jpg

crab.jpg

7942 ms

lobster.jpg

lobster.jpg

10424 ms

scallop.jpg

scallop.jpg

1483 ms

pekingduck.jpg

pekingduck.jpg

10217 ms

chicken.jpg

chicken.jpg

4961 ms

dimsum2.jpg

dimsum2.jpg

5171 ms

dinner.jpg

dinner.jpg

1636 ms

setmenu.jpg

setmenu.jpg

2299 ms

veg.png

veg.png

3098 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3018 ms

www-widgetapi.js

www-widgetapi.js

227 ms

iframe_api

iframe_api

463 ms

admin-ajax.php

admin-ajax.php

3499 ms

ajax-loader.gif

ajax-loader.gif

1890 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

2040 ms

icomoon.woff

icomoon.woff

3536 ms

Accessibility Review

floata.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

floata.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

floata.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floata.com 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 Floata.com 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.

Social Sharing Optimization

floata.com

Open Graph description is not detected on the main page of Floata. 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: