Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

fluvalblog.com

Home Page - Fluvalaquatics

Page Load Speed

1.1 sec in total

First Response

99 ms

Resources Loaded

797 ms

Page Rendered

192 ms

fluvalblog.com screenshot

About Website

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

The Home Aquarium Brand. For over 30 years, Fluval aquatic products have earned the trust of fish hobbyists by making smart products that provide many valuable benefits.

Visit fluvalblog.com

Key Findings

We analyzed Fluvalblog.com page load time and found that the first response time was 99 ms and then it took 989 ms 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.

Performance Metrics

fluvalblog.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.232

54/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

fluvalblog.com

99 ms

fluvalaquatics.com

99 ms

reset.css

40 ms

fontface.css

88 ms

default_landing.css

75 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Fluvalblog.com, 65% (15 requests) were made to Fluvalaquatics.com and 9% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (169 ms) relates to the external source Fluvalaquatics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.4 kB (37%)

Content Size

723.4 kB

After Optimization

453.1 kB

In fact, the total size of Fluvalblog.com main page is 723.4 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. 20% of websites need less resources to load. Javascripts take 374.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 4.2 kB

  • Original 6.0 kB
  • After minification 5.6 kB
  • After compression 1.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. 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 4.2 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 4.5 kB

  • Original 337.1 kB
  • After minification 332.6 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. Fluvalblog images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 257.9 kB

  • Original 374.9 kB
  • After minification 362.3 kB
  • After compression 117.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 257.9 kB or 69% of the original size.

CSS Optimization

-69%

Potential reduce by 3.8 kB

  • Original 5.4 kB
  • After minification 4.7 kB
  • After compression 1.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. Fluvalblog.com needs all CSS files to be minified and compressed as it can save up to 3.8 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (24%)

Requests Now

17

After Optimization

13

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

Accessibility Review

fluvalblog.com accessibility score

100

Accessibility Issues

Best Practices

fluvalblog.com best practices score

75

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

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

fluvalblog.com SEO score

93

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

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

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