Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

sparkz.energy

Manufacturing Cathode Material | Sparkz Inc.

Page Load Speed

946 ms in total

First Response

27 ms

Resources Loaded

341 ms

Page Rendered

578 ms

About Website

Welcome to sparkz.energy homepage info - get ready to check Sparkz best content right away, or after learning these important things about sparkz.energy

Sparkz is at the forefront of manufacturing Cathode Active Material (CAM) for nickel free and cobalt free lithium batteries in the U.S.

Visit sparkz.energy

Key Findings

We analyzed Sparkz.energy page load time and found that the first response time was 27 ms and then it took 919 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

sparkz.energy performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value900 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.661

8/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

sparkz.energy

27 ms

sparkz.energy

46 ms

custom-color-overrides.css

14 ms

ie.css

40 ms

elementor-icons.min.css

28 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 Sparkz.energy, 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 (167 ms) belongs to the original domain Sparkz.energy.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

1.5 MB

In fact, the total size of Sparkz.energy main page is 2.8 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. 35% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 64.9 kB

  • Original 79.4 kB
  • After minification 77.8 kB
  • After compression 14.6 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 64.9 kB or 82% of the original size.

Image Optimization

-47%

Potential reduce by 1.2 MB

  • Original 2.5 MB
  • After minification 1.4 MB

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, Sparkz needs image optimization as it can save up to 1.2 MB or 47% 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 1.3 kB

  • Original 97.0 kB
  • After minification 97.0 kB
  • After compression 95.7 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

-8%

Potential reduce by 6.2 kB

  • Original 79.8 kB
  • After minification 79.6 kB
  • After compression 73.6 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. Sparkz.energy has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (88%)

Requests Now

32

After Optimization

4

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

Accessibility Review

sparkz.energy accessibility score

100

Accessibility Issues

Best Practices

sparkz.energy 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

sparkz.energy 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 Sparkz.energy 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 Sparkz.energy 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 data is detected on the main page of Sparkz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: