Tools & Wizards About Us
bouncingfish.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

bouncingfish.com

Jason Kneen - Freelance App Developer, UK, iOS, Android, iPhone, iPad

Page Load Speed

4.6 sec in total

First Response

232 ms

Resources Loaded

3.8 sec

Page Rendered

663 ms

bouncingfish.com screenshot

About Website

Click here to check amazing Bouncingfish content. Otherwise, check out these important facts you probably never knew about bouncingfish.com

UK based Freelance App Developer and mobile consultant, building cross-platform Native Mobile Apps for iOS, Android, iPhone, iPad and Apple Watch.

Visit bouncingfish.com

Key Findings

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

Performance Metrics

bouncingfish.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

bouncingfish.com

232 ms

bouncingfish.com

1110 ms

www.bouncingfish.com

198 ms

www.bouncingfish.com

601 ms

bootstrap.css

344 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 80% of them (45 requests) were addressed to the original Bouncingfish.com, 11% (6 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Bouncingfish.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 398.7 kB (12%)

Content Size

3.2 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 22.5 kB

  • Original 28.3 kB
  • After minification 20.6 kB
  • After compression 5.8 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. This page needs HTML code to be minified as it can gain 7.6 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.5 kB or 80% of the original size.

Image Optimization

-12%

Potential reduce by 354.3 kB

  • Original 3.1 MB
  • After minification 2.7 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. Obviously, Bouncingfish needs image optimization as it can save up to 354.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-15%

Potential reduce by 11.2 kB

  • Original 74.0 kB
  • After minification 74.0 kB
  • After compression 62.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 11.2 kB or 15% of the original size.

CSS Optimization

-30%

Potential reduce by 10.7 kB

  • Original 35.7 kB
  • After minification 35.6 kB
  • After compression 24.9 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. Bouncingfish.com needs all CSS files to be minified and compressed as it can save up to 10.7 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (22%)

Requests Now

45

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bouncingfish.com

bouncingfish.com

232 ms

bouncingfish.com

bouncingfish.com

1110 ms

www.bouncingfish.com

www.bouncingfish.com

198 ms

www.bouncingfish.com

www.bouncingfish.com

601 ms

bootstrap.css

bootstrap.css

344 ms

responsive.css

responsive.css

295 ms

font-awesome.css

font-awesome.css

310 ms

theme.css

theme.css

312 ms

fonts.css

fonts.css

287 ms

jquery.min.js

jquery.min.js

662 ms

bootstrap.js

bootstrap.js

459 ms

script.js

script.js

420 ms

css

css

39 ms

assistantLoader.latest.js

assistantLoader.latest.js

66 ms

bouncingfish.png

bouncingfish.png

234 ms

jason.jpeg

jason.jpeg

285 ms

litterlotto-hero.jpg

litterlotto-hero.jpg

687 ms

helpmeangela640x400.jpg

helpmeangela640x400.jpg

506 ms

walksafe640x400.png

walksafe640x400.png

584 ms

opus640x400.png

opus640x400.png

462 ms

ses640x400.png

ses640x400.png

889 ms

betconnect640x400.png

betconnect640x400.png

607 ms

cookbook600x400.png

cookbook600x400.png

624 ms

thedealer600x400.jpg

thedealer600x400.jpg

652 ms

jobswipe600x400.jpg

jobswipe600x400.jpg

708 ms

forghetti640x400.png

forghetti640x400.png

819 ms

bootcamp600x400.jpg

bootcamp600x400.jpg

771 ms

cima600x400.png

cima600x400.png

770 ms

uktvplay-600x400.jpg

uktvplay-600x400.jpg

799 ms

honda600x400.jpg

honda600x400.jpg

832 ms

stonehenge600x400.jpg

stonehenge600x400.jpg

884 ms

dentons2-600x400.jpg

dentons2-600x400.jpg

913 ms

honda.png

honda.png

897 ms

appcelerator.png

appcelerator.png

940 ms

sixpack.png

sixpack.png

962 ms

itv.png

itv.png

1007 ms

yougov.png

yougov.png

1004 ms

bedbathbeyond.png

bedbathbeyond.png

1008 ms

sotl.png

sotl.png

1072 ms

brewdog.png

brewdog.png

1073 ms

caremeds.png

caremeds.png

1097 ms

EMC-logo.png

EMC-logo.png

1136 ms

karcher-logo.png

karcher-logo.png

1131 ms

antenna.png

antenna.png

1161 ms

noisy_grey.png

noisy_grey.png

1219 ms

grey_pattern.png

grey_pattern.png

1190 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

35 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

48 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

48 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1162 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

48 ms

ga.js

ga.js

35 ms

__utm.gif

__utm.gif

12 ms

zqmkb3d3

zqmkb3d3

35 ms

Accessibility Review

bouncingfish.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

bouncingfish.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

bouncingfish.com SEO score

87

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

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

High

Tap targets are not sized appropriately

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 Bouncingfish.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 Bouncingfish.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

bouncingfish.com

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