Tools & Wizards About Us

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

howtobuildafloatingisland.com

How to make a floating planted pond island: instructions for floating pond planters.

Page Load Speed

21.7 sec in total

First Response

375 ms

Resources Loaded

20.5 sec

Page Rendered

810 ms

About Website

Welcome to howtobuildafloatingisland.com homepage info - get ready to check Howtobuilda Floating Island best content right away, or after learning these important things about howtobuildafloatingisland.com

Instructions and materials list to make a floating island planter for your pond or water garden. Easy and inexpensive way to make a natural looking flaoting pond island with real plants!

Visit howtobuildafloatingisland.com

Key Findings

We analyzed Howtobuildafloatingisland.com page load time and found that the first response time was 375 ms and then it took 21.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. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

howtobuildafloatingisland.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value5,380 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

howtobuildafloatingisland.com

375 ms

cut-out-stencil-for-floating-island-shapeth2.jpg

609 ms

cut-out-shape-on-pond-filter-material-for-floating-islandths.jpg

615 ms

cut-two-layers-of-filter-from-template-floating-islandths.jpg

680 ms

sewing-floating-islands-togetherths.jpg

608 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 36% of them (16 requests) were addressed to the original Howtobuildafloatingisland.com, 13% (6 requests) were made to Assoc-amazon.com and 9% (4 requests) were made to Htmlcommentbox.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Assoc-amazon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.3 kB (18%)

Content Size

755.5 kB

After Optimization

619.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Howtobuildafloatingisland.com main page is 755.5 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. 30% of websites need less resources to load. Images take 602.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 114.7 kB

  • Original 147.0 kB
  • After minification 138.6 kB
  • After compression 32.3 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 114.7 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 20.8 kB

  • Original 602.1 kB
  • After minification 581.2 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. Howtobuilda Floating Island images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 842 B

  • Original 1.7 kB
  • After minification 1.6 kB
  • After compression 863 B

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 842 B or 49% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 4.7 kB
  • After minification 4.7 kB
  • After compression 4.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. Howtobuildafloatingisland.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

34

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

howtobuildafloatingisland.com accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

howtobuildafloatingisland.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

howtobuildafloatingisland.com SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Howtobuildafloatingisland.com 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 Howtobuildafloatingisland.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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