Tools & Wizards About Us
fuelless.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fuelless.com

Creative Science & Research | build a free energy motor

Page Load Speed

1.1 sec in total

First Response

82 ms

Resources Loaded

982 ms

Page Rendered

51 ms

fuelless.com screenshot

About Website

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

The Fuelless Engine M2 - Free energy Motor/generator. Since 1996. Go off Grid with our M2 Motor. Perfect for researchers and home owners. MOTORS – GENERATORS – NEW DISCOVERIES - Alternative Energy. Cr...

Visit fuelless.com

Key Findings

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

fuelless.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value2,970 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

www.fuelless.com

82 ms

minified.js

26 ms

focus-within-polyfill.js

23 ms

polyfill.min.js

63 ms

thunderbolt-commons.7700cd07.bundle.min.js

169 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fuelless.com, 25% (14 requests) were made to Static.parastorage.com and 25% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (612 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (45%)

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fuelless.com main page is 2.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 875.3 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 204.0 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 875.3 kB or 81% of the original size.

Image Optimization

-24%

Potential reduce by 214.7 kB

  • Original 889.3 kB
  • After minification 674.5 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. Obviously, Fuelless needs image optimization as it can save up to 214.7 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 6.1 kB

  • Original 426.4 kB
  • After minification 426.4 kB
  • After compression 420.3 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

-0%

Potential reduce by 0 B

  • Original 59.9 kB
  • After minification 59.9 kB
  • After compression 59.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. Fuelless.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (45%)

Requests Now

33

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.fuelless.com

www.fuelless.com

82 ms

minified.js

minified.js

26 ms

focus-within-polyfill.js

focus-within-polyfill.js

23 ms

polyfill.min.js

polyfill.min.js

63 ms

thunderbolt-commons.7700cd07.bundle.min.js

thunderbolt-commons.7700cd07.bundle.min.js

169 ms

main.16c08821.bundle.min.js

main.16c08821.bundle.min.js

170 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

152 ms

lodash.min.js

lodash.min.js

151 ms

react.production.min.js

react.production.min.js

44 ms

react-dom.production.min.js

react-dom.production.min.js

170 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

169 ms

100086_51b34e5daeb240079505274069030f12~mv2.jpg

100086_51b34e5daeb240079505274069030f12~mv2.jpg

596 ms

etLPhs1ChAU

etLPhs1ChAU

233 ms

bundle.min.js

bundle.min.js

96 ms

100086_0e0ab53d047d4e56a3e7f17d2492d7c0f000.jpg

100086_0e0ab53d047d4e56a3e7f17d2492d7c0f000.jpg

528 ms

100086_8ce888cb01f84bb086aaadc17d00bd09~mv2.png

100086_8ce888cb01f84bb086aaadc17d00bd09~mv2.png

55 ms

100086_0b8afa445d484a55bd3f7386e852a7f5~mv2.png

100086_0b8afa445d484a55bd3f7386e852a7f5~mv2.png

530 ms

100086_13aabc6bc93142d1830a98a058ee00e2~mv2.jpg

100086_13aabc6bc93142d1830a98a058ee00e2~mv2.jpg

527 ms

100086_60bb210f296f4fc0870cff3508d57695~mv2.jpg

100086_60bb210f296f4fc0870cff3508d57695~mv2.jpg

263 ms

100086_ad2d6a6965774f63b92035e486a3387a~mv2.jpg

100086_ad2d6a6965774f63b92035e486a3387a~mv2.jpg

529 ms

100086_3cc3a69126c24fedbec61aec7687a316~mv2.jpg

100086_3cc3a69126c24fedbec61aec7687a316~mv2.jpg

264 ms

100086_018cd4994faf4673b1db182200ba4d7b~mv2.png

100086_018cd4994faf4673b1db182200ba4d7b~mv2.png

566 ms

100086_262deef3424d42169531feb3829e47f4~mv2.jpg

100086_262deef3424d42169531feb3829e47f4~mv2.jpg

529 ms

100086_90c7721970704382a16784ad403666bd~mv2.png

100086_90c7721970704382a16784ad403666bd~mv2.png

612 ms

100086_0ab6eb9b25a64ae9a968ebb556826dd2~mv2.jpg

100086_0ab6eb9b25a64ae9a968ebb556826dd2~mv2.jpg

527 ms

100086_cfbf471759d345d494ded3db9e672b06~mv2.jpg

100086_cfbf471759d345d494ded3db9e672b06~mv2.jpg

562 ms

100086_60bb210f296f4fc0870cff3508d57695~mv2.jpg

100086_60bb210f296f4fc0870cff3508d57695~mv2.jpg

529 ms

355 ms

353 ms

353 ms

353 ms

349 ms

349 ms

480 ms

477 ms

476 ms

479 ms

479 ms

477 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

17 ms

AvenirLTW05-35Light.woff

AvenirLTW05-35Light.woff

18 ms

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

61bd362e-7162-46bd-b67e-28f366c4afbe.woff

17 ms

AvenirLTW05-85Heavy.woff

AvenirLTW05-85Heavy.woff

17 ms

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

cca525a8-ad89-43ae-aced-bcb49fb271dc.woff

16 ms

www-player.css

www-player.css

16 ms

www-embed-player.js

www-embed-player.js

60 ms

base.js

base.js

87 ms

ad_status.js

ad_status.js

172 ms

SdShMpdhHIYiz4OAK3X60VwAo5runEsW3RCnPxmRbSs.js

SdShMpdhHIYiz4OAK3X60VwAo5runEsW3RCnPxmRbSs.js

122 ms

embed.js

embed.js

46 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

43 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

45 ms

id

id

27 ms

Create

Create

12 ms

qoe

qoe

13 ms

log_event

log_event

0 ms

Accessibility Review

fuelless.com accessibility score

90

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

fuelless.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fuelless.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 Fuelless.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 Fuelless.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

fuelless.com

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