Tools & Wizards About Us
flaire.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

flaire.com

Flaire Marketing: Managed Marketing Automation for Small B2B Businesses

Page Load Speed

1.4 sec in total

First Response

215 ms

Resources Loaded

1 sec

Page Rendered

138 ms

flaire.com screenshot

About Website

Welcome to flaire.com homepage info - get ready to check Flaire best content right away, or after learning these important things about flaire.com

Flaire Marketing provides managed marketing automation for small B2B companies throughout the Midwest, but is not limited by geography. Clients rely on OUR team of marketing automation experts.

Visit flaire.com

Key Findings

We analyzed Flaire.com page load time and found that the first response time was 215 ms and then it took 1.2 sec 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

flaire.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

www.flaire.com

215 ms

analytics.js

27 ms

wp-emoji-release.min.js

22 ms

style.min.css

23 ms

style.css

30 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 80% of them (32 requests) were addressed to the original Flaire.com, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (298 ms) relates to the external source Marketing.flaire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 691.1 kB (75%)

Content Size

922.8 kB

After Optimization

231.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 24.0 kB

  • Original 32.3 kB
  • After minification 30.6 kB
  • After compression 8.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 24.0 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 2.2 kB

  • Original 64.9 kB
  • After minification 62.7 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. Flaire images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 362.2 kB

  • Original 473.9 kB
  • After minification 356.6 kB
  • After compression 111.6 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 362.2 kB or 76% of the original size.

CSS Optimization

-86%

Potential reduce by 302.7 kB

  • Original 351.7 kB
  • After minification 289.9 kB
  • After compression 49.0 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. Flaire.com needs all CSS files to be minified and compressed as it can save up to 302.7 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

35

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.flaire.com

www.flaire.com

215 ms

analytics.js

analytics.js

27 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

22 ms

style.min.css

style.min.css

23 ms

style.css

style.css

30 ms

bootstrap.css

bootstrap.css

44 ms

animate.css

animate.css

36 ms

responsive.css

responsive.css

23 ms

font-awesome.css

font-awesome.css

26 ms

css

css

23 ms

frontend.min.js

frontend.min.js

28 ms

jquery.js

jquery.js

53 ms

jquery-migrate.min.js

jquery-migrate.min.js

37 ms

bootstrap.js

bootstrap.js

64 ms

jquery.smartmenus.js

jquery.smartmenus.js

37 ms

jquery.smartmenus.bootstrap.js

jquery.smartmenus.bootstrap.js

68 ms

imgLiquid.js

imgLiquid.js

69 ms

modernizr.js

modernizr.js

74 ms

stickUp.js

stickUp.js

88 ms

sticky.js

sticky.js

74 ms

wow.js

wow.js

87 ms

custom.js

custom.js

86 ms

unslider.js

unslider.js

73 ms

jquery.flexslider.js

jquery.flexslider.js

100 ms

ideal-image-slider.js

ideal-image-slider.js

101 ms

iis-captions.js

iis-captions.js

101 ms

scrollup.js

scrollup.js

101 ms

animation.js

animation.js

101 ms

slides.js

slides.js

101 ms

slides-captions.js

slides-captions.js

110 ms

wp-embed.min.js

wp-embed.min.js

110 ms

collect

collect

82 ms

collect

collect

149 ms

FMMAlogo.jpg

FMMAlogo.jpg

103 ms

tablet-313002_640.jpg

tablet-313002_640.jpg

18 ms

js

js

122 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

28 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

15 ms

29539

29539

298 ms

Accessibility Review

flaire.com accessibility score

92

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

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

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

    EN

  • Encoding

    UTF-8

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

flaire.com

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