Tools & Wizards About Us
fldn.tv screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fldn.tv

Floodin. Easy video and photo sales for adventure guides

Page Load Speed

6.1 sec in total

First Response

193 ms

Resources Loaded

5.2 sec

Page Rendered

688 ms

fldn.tv screenshot

About Website

Click here to check amazing Fldn content for South Africa. Otherwise, check out these important facts you probably never knew about fldn.tv

Floodin makes it easy to publish videos and photos of your guided activities and deliver them to your guests. Capture - Upload - Deliver - Share

Visit fldn.tv

Key Findings

We analyzed Fldn.tv page load time and found that the first response time was 193 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fldn.tv performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

fldn.tv

193 ms

floodin.com

938 ms

nprogress.min.css

25 ms

4d3ae897358f81e0.css

260 ms

836c24faaf4e870d.css

496 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fldn.tv, 88% (56 requests) were made to Floodin.com and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Floodin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.0 kB (3%)

Content Size

2.1 MB

After Optimization

2.1 MB

  • HTML
  • Images

In fact, the total size of Fldn.tv main page is 2.1 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 30.3 kB

  • Original 38.3 kB
  • After minification 38.2 kB
  • After compression 8.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 30.3 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 41.7 kB

  • Original 2.1 MB
  • After minification 2.1 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. Fldn images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 20 (36%)

Requests Now

56

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fldn.tv

fldn.tv

193 ms

floodin.com

floodin.com

938 ms

nprogress.min.css

nprogress.min.css

25 ms

4d3ae897358f81e0.css

4d3ae897358f81e0.css

260 ms

836c24faaf4e870d.css

836c24faaf4e870d.css

496 ms

c3bb5f363cf93a83.css

c3bb5f363cf93a83.css

723 ms

57e822db21be3c4d.css

57e822db21be3c4d.css

883 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

1230 ms

webpack-acf78cd771e8e731.js

webpack-acf78cd771e8e731.js

1008 ms

framework-91d7f78b5b4003c8.js

framework-91d7f78b5b4003c8.js

1196 ms

main-fa96892c8b871084.js

main-fa96892c8b871084.js

1227 ms

_app-9a5df0aeb3747a20.js

_app-9a5df0aeb3747a20.js

1030 ms

1bfc9850-5b429273a5fbe9ba.js

1bfc9850-5b429273a5fbe9ba.js

1105 ms

304-cac8e7e2395cc3d4.js

304-cac8e7e2395cc3d4.js

1270 ms

38-2025099a63c84e20.js

38-2025099a63c84e20.js

1271 ms

151-805d84283645d36c.js

151-805d84283645d36c.js

1569 ms

66-e41b0f651ef306a2.js

66-e41b0f651ef306a2.js

1462 ms

679-ea85fa6f53ae4007.js

679-ea85fa6f53ae4007.js

1504 ms

455-54ccd7713802f459.js

455-54ccd7713802f459.js

1503 ms

527-a1d9b7c31e9e66ee.js

527-a1d9b7c31e9e66ee.js

1496 ms

index-583feb4e93a7fafc.js

index-583feb4e93a7fafc.js

1537 ms

_buildManifest.js

_buildManifest.js

1685 ms

_ssgManifest.js

_ssgManifest.js

1720 ms

_middlewareManifest.js

_middlewareManifest.js

1785 ms

floodin-white-logo.svg

floodin-white-logo.svg

1788 ms

google-play-badge.png

google-play-badge.png

1815 ms

ios-desktop.png

ios-desktop.png

1818 ms

qr-code.png

qr-code.png

1909 ms

footage-cat.jpg

footage-cat.jpg

2161 ms

footage-gray-heart.svg

footage-gray-heart.svg

2008 ms

footage-gray-chat.svg

footage-gray-chat.svg

2019 ms

footage-likes.png

footage-likes.png

2035 ms

footage-happy-face.svg

footage-happy-face.svg

2038 ms

footage-family.jpg

footage-family.jpg

3020 ms

footage-waffle.jpg

footage-waffle.jpg

2447 ms

check-icon.png

check-icon.png

2238 ms

simple-phone.png

simple-phone.png

3321 ms

9.png

9.png

2275 ms

10.png

10.png

2386 ms

11.png

11.png

2209 ms

12.png

12.png

2008 ms

13.png

13.png

1897 ms

range-slider.png

range-slider.png

1224 ms

14.png

14.png

1707 ms

pxiByp8kv8JHgFVrLEj6V1g.woff

pxiByp8kv8JHgFVrLEj6V1g.woff

22 ms

pxiByp8kv8JHgFVrLCz7V1g.woff

pxiByp8kv8JHgFVrLCz7V1g.woff

37 ms

pxiByp8kv8JHgFVrLDD4V1g.woff

pxiByp8kv8JHgFVrLDD4V1g.woff

45 ms

pxiByp8kv8JHgFVrLBT5V1g.woff

pxiByp8kv8JHgFVrLBT5V1g.woff

57 ms

pxiByp8kv8JHgFVrLGT9V1g.woff

pxiByp8kv8JHgFVrLGT9V1g.woff

58 ms

pxiEyp8kv8JHgFVrFJM.woff

pxiEyp8kv8JHgFVrFJM.woff

57 ms

15.png

15.png

1683 ms

16.png

16.png

1688 ms

17.png

17.png

1743 ms

18.png

18.png

1705 ms

19.png

19.png

1692 ms

20.png

20.png

1682 ms

21.png

21.png

1818 ms

22.png

22.png

1856 ms

23.png

23.png

1688 ms

24.png

24.png

1692 ms

25.png

25.png

1748 ms

26.png

26.png

1808 ms

lets-do-this.png

lets-do-this.png

1817 ms

calculator.b10318b5.png

calculator.b10318b5.png

1800 ms

Accessibility Review

fldn.tv accessibility score

75

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fldn.tv best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fldn.tv SEO score

92

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

    N/A

  • Encoding

    UTF-8

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

fldn.tv

Open Graph data is detected on the main page of Fldn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: