Tools & Wizards About Us
flaer.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% 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

  • 93

    SEO

    Google-friendlier than
    83% of websites

flaer.com

Flaér - Ride faster, ride further, recover quicker

Page Load Speed

3.5 sec in total

First Response

298 ms

Resources Loaded

2.5 sec

Page Rendered

672 ms

flaer.com screenshot

About Website

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

The world’s first chain performance system for bikes. Chain performance systems ensure your transmission operates at maximum efficiency.

Visit flaer.com

Key Findings

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

Performance Metrics

flaer.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.236

53/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

flaer.com

298 ms

flaer.com

1057 ms

styles.css

302 ms

css2

31 ms

style.min.css

574 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 92% of them (34 requests) were addressed to the original Flaer.com, 5% (2 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Flaer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 763.0 kB (40%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 31.0 kB

  • Original 40.7 kB
  • After minification 38.6 kB
  • After compression 9.7 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 31.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 557 B

  • Original 945.8 kB
  • After minification 945.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. Flaer images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 306.6 kB

  • Original 433.4 kB
  • After minification 433.4 kB
  • After compression 126.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 306.6 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 424.9 kB

  • Original 510.1 kB
  • After minification 509.0 kB
  • After compression 85.2 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. Flaer.com needs all CSS files to be minified and compressed as it can save up to 424.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (68%)

Requests Now

28

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flaer.com

flaer.com

298 ms

flaer.com

flaer.com

1057 ms

styles.css

styles.css

302 ms

css2

css2

31 ms

style.min.css

style.min.css

574 ms

styles.css

styles.css

291 ms

jquery.min.js

jquery.min.js

485 ms

jquery-migrate.min.js

jquery-migrate.min.js

300 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

300 ms

add-to-cart.min.js

add-to-cart.min.js

389 ms

js.cookie.min.js

js.cookie.min.js

401 ms

woocommerce.min.js

woocommerce.min.js

401 ms

scripts.js

scripts.js

499 ms

hero.css

hero.css

745 ms

box-links.css

box-links.css

743 ms

page-content.css

page-content.css

742 ms

featured-products.css

featured-products.css

742 ms

comment-reply.min.js

comment-reply.min.js

742 ms

index.js

index.js

743 ms

index.js

index.js

744 ms

sourcebuster.min.js

sourcebuster.min.js

744 ms

order-attribution.min.js

order-attribution.min.js

744 ms

forms.js

forms.js

745 ms

part-3-pic-2-1750x1000.jpeg

part-3-pic-2-1750x1000.jpeg

421 ms

Revo-Via-Kit-300x198.png

Revo-Via-Kit-300x198.png

326 ms

revo-terra-300x206.jpeg

revo-terra-300x206.jpeg

253 ms

guard-product-cut-out-1-272x300.png

guard-product-cut-out-1-272x300.png

326 ms

Flaer-Spares-and-Adapters-300x185.jpg

Flaer-Spares-and-Adapters-300x185.jpg

253 ms

via-and-terra-together-e1690201135244-300x288.png

via-and-terra-together-e1690201135244-300x288.png

253 ms

paypal_icon.png

paypal_icon.png

326 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf

146 ms

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf

148 ms

fa-brands-400.woff

fa-brands-400.woff

264 ms

fa-solid-900.woff

fa-solid-900.woff

255 ms

fa-regular-400.woff

fa-regular-400.woff

371 ms

FoundersGrotesk-Bold.woff

FoundersGrotesk-Bold.woff

110 ms

FoundersGrotesk-BoldItalic.woff

FoundersGrotesk-BoldItalic.woff

110 ms

Accessibility Review

flaer.com accessibility score

86

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

flaer.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 Flaer.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 Flaer.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

flaer.com

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