Tools & Wizards About Us
finico.com screenshot

Report Summary

  • 83

    Performance

    Renders faster than
    87% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

finico.com

Tembi products - Wood finishing products canadian distributor

Page Load Speed

849 ms in total

First Response

81 ms

Resources Loaded

658 ms

Page Rendered

110 ms

finico.com screenshot

About Website

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

Tembi Products is constantly innovating on designing, transforming and distributing wood finishing quality products with smaller impact on users environment.

Visit finico.com

Key Findings

We analyzed Finico.com page load time and found that the first response time was 81 ms and then it took 768 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

finico.com performance score

83

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

finico.com

81 ms

62 ms

wey5qen.js

136 ms

6f1efb3d6ccd.css

44 ms

857b6d37b82c.js

78 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 Finico.com, 52% (12 requests) were made to Tembi.ca and 22% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (250 ms) relates to the external source Tembi.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 16.0 kB (6%)

Content Size

267.7 kB

After Optimization

251.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 7.9 kB

  • Original 10.4 kB
  • After minification 8.4 kB
  • After compression 2.5 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 2.0 kB, which is 19% 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 7.9 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 2.2 kB

  • Original 208.5 kB
  • After minification 206.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. Finico images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 75 B

  • Original 22.3 kB
  • After minification 22.3 kB
  • After compression 22.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-22%

Potential reduce by 5.8 kB

  • Original 26.6 kB
  • After minification 26.6 kB
  • After compression 20.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. Finico.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (29%)

Requests Now

17

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Finico. 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 as a result speed up the page load time.

Network Requests Diagram

finico.com

finico.com

81 ms

62 ms

wey5qen.js

wey5qen.js

136 ms

6f1efb3d6ccd.css

6f1efb3d6ccd.css

44 ms

857b6d37b82c.js

857b6d37b82c.js

78 ms

3d53f7dcd7a0.js

3d53f7dcd7a0.js

161 ms

analytics.js

analytics.js

78 ms

logo-prato-verde.a2c0b728fdba.png

logo-prato-verde.a2c0b728fdba.png

75 ms

Pareo_Zero_2-946mL_webFB.327188.png

Pareo_Zero_2-946mL_webFB.327188.png

130 ms

Brio_Zero_2-946mL_webFB.4229b4.png

Brio_Zero_2-946mL_webFB.4229b4.png

75 ms

Secondo_Mono_2-946mL_webFB.395362.png

Secondo_Mono_2-946mL_webFB.395362.png

106 ms

Secondo_Clean_946mL_web.fb7453.png

Secondo_Clean_946mL_web.fb7453.png

141 ms

Secondo_Maintenance_946mL_web.bc8d11.png

Secondo_Maintenance_946mL_web.bc8d11.png

121 ms

Tavolo_2-500mL_webFB.e66926.png

Tavolo_2-500mL_webFB.e66926.png

144 ms

Nettoyeur_doutils_946ml_webFB.c421ec.png

Nettoyeur_doutils_946ml_webFB.c421ec.png

250 ms

d

d

20 ms

d

d

37 ms

d

d

31 ms

d

d

31 ms

ec.js

ec.js

12 ms

collect

collect

15 ms

js

js

66 ms

p.gif

p.gif

21 ms

Accessibility Review

finico.com accessibility score

86

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

Best Practices

finico.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

finico.com SEO score

100

Search Engine Optimization Advices

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

finico.com

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