1.2 sec in total
109 ms
886 ms
232 ms
Click here to check amazing Floating World content for Egypt. Otherwise, check out these important facts you probably never knew about floatingworld.ca
Web and Mobile app development company based in Comox, BC. Angular, node.js, wordpress, PHP. Custom coding and web development.
Visit floatingworld.caWe analyzed Floatingworld.ca page load time and found that the first response time was 109 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 20% of websites can load faster.
floatingworld.ca performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.7 s
31/100
25%
Value5.5 s
55/100
10%
Value210 ms
88/100
30%
Value0.49
17/100
15%
Value6.3 s
61/100
10%
109 ms
14 ms
15 ms
15 ms
17 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 78% of them (84 requests) were addressed to the original Floatingworld.ca, 7% (8 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (490 ms) belongs to the original domain Floatingworld.ca.
Page size can be reduced by 339.4 kB (44%)
769.1 kB
429.8 kB
In fact, the total size of Floatingworld.ca main page is 769.1 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. 65% of websites need less resources to load. Images take 380.0 kB which makes up the majority of the site volume.
Potential reduce by 67.0 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 67.0 kB or 82% of the original size.
Potential reduce by 62.7 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. Obviously, Floating World needs image optimization as it can save up to 62.7 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 87.0 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 87.0 kB or 57% of the original size.
Potential reduce by 122.8 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. Floatingworld.ca needs all CSS files to be minified and compressed as it can save up to 122.8 kB or 79% of the original size.
Number of requests can be reduced by 57 (58%)
98
41
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floating World. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
floatingworld.ca
109 ms
system.base.css
14 ms
system.menus.css
15 ms
system.messages.css
15 ms
system.theme.css
17 ms
aggregator.css
18 ms
comment.css
17 ms
field.css
20 ms
node.css
19 ms
search.css
20 ms
user.css
22 ms
views.css
21 ms
ctools.css
20 ms
jquerymenu.css
26 ms
panels.css
22 ms
flexslider.css
23 ms
flexslider_img.css
26 ms
responsive_menus_simple.css
27 ms
quicktabs.css
26 ms
alpha-reset.css
27 ms
alpha-mobile.css
29 ms
alpha-alpha.css
28 ms
formalize.css
29 ms
omega-text.css
30 ms
omega-branding.css
29 ms
omega-menu.css
30 ms
omega-forms.css
36 ms
omega-visuals.css
31 ms
global.css
32 ms
floatingworld-alpha-default-narrow.css
37 ms
alpha-default-narrow-12.css
36 ms
floatingworld-alpha-default-normal.css
36 ms
alpha-default-normal-12.css
38 ms
floatingworld-alpha-default-wide.css
37 ms
alpha-default-wide-12.css
38 ms
css
48 ms
jquery-1.7.1.js
33 ms
LoginRadius.js
69 ms
jquery.once.js
36 ms
drupal.js
35 ms
progress.js
34 ms
jquerymenu.js
33 ms
less-display.js
32 ms
less-1.3.0.min.js
34 ms
panels.js
33 ms
jquery.flexslider-min.js
31 ms
responsive_menus_simple.js
30 ms
googleanalytics.js
31 ms
quicktabs.js
30 ms
jquery.formalize.js
30 ms
omega-mediaqueries.js
30 ms
omega-equalheights.js
29 ms
flexslider.load.js
28 ms
ga.js
29 ms
LoginRadius.js
20 ms
style.css
23 ms
__utm.gif
137 ms
bg_navbar.png
128 ms
all.js
21 ms
in.js
95 ms
platform.js
67 ms
floatingworld_logo.png
18 ms
new-header.jpg
19 ms
starburst-for-web_0.png
30 ms
moneytalks.jpg
18 ms
sixteen.jpg
15 ms
novex.jpg
16 ms
iwm.jpg
21 ms
cansel.jpg
19 ms
doctor-decisions.jpg
18 ms
green-bull.jpg
20 ms
voices_of_toronto.jpg
20 ms
efw.jpg
22 ms
eco-geek.jpg
20 ms
sanctuary-for-kids.jpg
23 ms
afar.jpg
22 ms
earls.jpg
22 ms
fmconstructions.jpg
24 ms
cpc.jpg
23 ms
bg_body.png
25 ms
bg_services.png
490 ms
silohuettes-for-web.png
24 ms
bg_testimonial_bubble.png
25 ms
work-earls.jpg
26 ms
work-cansel.jpg
26 ms
work-cpc.jpg
27 ms
work-monytalks.jpg
53 ms
bg_footer_tile.jpg
50 ms
social_buttons.png
52 ms
bg_subscribe_highlight.png
52 ms
bg_subscribe.png
53 ms
subscribe_button.png
53 ms
logo-slider-navigation.png
54 ms
list-green-dot.jpg
54 ms
logo.png
19 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
54 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
55 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
84 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
84 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
84 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
85 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
84 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
82 ms
129 ms
xd_arbiter.php
39 ms
xd_arbiter.php
46 ms
secureAnonymousFramework
165 ms
ping
45 ms
floatingworld.ca 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
floatingworld.ca 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
floatingworld.ca 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floatingworld.ca 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 Floatingworld.ca 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.
floatingworld.ca
Open Graph description is not detected on the main page of Floating World. 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: