Tools & Wizards About Us
jasper.io screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jasper.io

Page Load Speed

1.8 sec in total

First Response

93 ms

Resources Loaded

812 ms

Page Rendered

944 ms

jasper.io screenshot

About Website

Visit jasper.io now to see the best up-to-date Jasper content for New Zealand and also check out these interesting facts you probably never knew about jasper.io

Visit jasper.io

Key Findings

We analyzed Jasper.io page load time and found that the first response time was 93 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

jasper.io performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value2,270 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.jasper.io

93 ms

911cfce3ac3efae4.css

36 ms

polyfills-c67a75d1b6f99dc8.js

81 ms

2511.23dfe698f28430fd.js

59 ms

6765.8fe01bbd6a048a53.js

55 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 67% of them (24 requests) were addressed to the original Jasper.io, 33% (12 requests) were made to Cdn.sanity.io. The less responsive or slowest element that took the longest time to load (697 ms) relates to the external source Cdn.sanity.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.5 kB (7%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images

In fact, the total size of Jasper.io main page is 1.4 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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 96.2 kB

  • Original 116.3 kB
  • After minification 116.3 kB
  • After compression 20.1 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 96.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 266 B

  • Original 1.2 MB
  • After minification 1.2 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. Jasper images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 31 (89%)

Requests Now

35

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.jasper.io

www.jasper.io

93 ms

911cfce3ac3efae4.css

911cfce3ac3efae4.css

36 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

81 ms

2511.23dfe698f28430fd.js

2511.23dfe698f28430fd.js

59 ms

6765.8fe01bbd6a048a53.js

6765.8fe01bbd6a048a53.js

55 ms

4701.f97c6790898fe4d4.js

4701.f97c6790898fe4d4.js

109 ms

1401.f7f305a83c732b3e.js

1401.f7f305a83c732b3e.js

61 ms

6016.b8fea22ba80e8200.js

6016.b8fea22ba80e8200.js

63 ms

8446.819caa66a6d45fa3.js

8446.819caa66a6d45fa3.js

54 ms

6890.c1a3b2c73f5864b1.js

6890.c1a3b2c73f5864b1.js

68 ms

9510-0433a68710e72364.js

9510-0433a68710e72364.js

152 ms

2486.55bd4216e94b2080.js

2486.55bd4216e94b2080.js

105 ms

8905.4011a2d45c405be7.js

8905.4011a2d45c405be7.js

104 ms

webpack-827e63c79598f4f8.js

webpack-827e63c79598f4f8.js

77 ms

framework-3f9946e1291d49a0.js

framework-3f9946e1291d49a0.js

104 ms

main-0c61f8e1e3764842.js

main-0c61f8e1e3764842.js

105 ms

_app-c286e285c5c19af3.js

_app-c286e285c5c19af3.js

192 ms

4683-e0974c4f915d9375.js

4683-e0974c4f915d9375.js

108 ms

2738-abba7b51f042e111.js

2738-abba7b51f042e111.js

108 ms

5851-46cd24a820ae520d.js

5851-46cd24a820ae520d.js

112 ms

index-18bf7f77612022d1.js

index-18bf7f77612022d1.js

131 ms

_buildManifest.js

_buildManifest.js

110 ms

_ssgManifest.js

_ssgManifest.js

124 ms

d5e7d91545fb1d6f87224913a278530015e2a108-2924x1950.jpg

d5e7d91545fb1d6f87224913a278530015e2a108-2924x1950.jpg

697 ms

d5e7d91545fb1d6f87224913a278530015e2a108-2924x1950.jpg

d5e7d91545fb1d6f87224913a278530015e2a108-2924x1950.jpg

200 ms

7364bf52efde4c2b82879119003cded813c25924-3536x2286.png

7364bf52efde4c2b82879119003cded813c25924-3536x2286.png

275 ms

e4ec1e895651e9d896527ac4aa8f9a894551f700-1147x651.png

e4ec1e895651e9d896527ac4aa8f9a894551f700-1147x651.png

263 ms

6e24db69372af1e2a6eba7fe782b85210b8f1c48-907x1048.jpg

6e24db69372af1e2a6eba7fe782b85210b8f1c48-907x1048.jpg

264 ms

815e5476f02c0eccbae701d396fb8ca3e5a2ff19-919x1034.png

815e5476f02c0eccbae701d396fb8ca3e5a2ff19-919x1034.png

262 ms

d55a8e274112307a93255ff9d1cc11512e514062-674x342.png

d55a8e274112307a93255ff9d1cc11512e514062-674x342.png

386 ms

932753798b38c11c7082c9d5e71287509ef295b6-674x342.png

932753798b38c11c7082c9d5e71287509ef295b6-674x342.png

424 ms

dee6f667bc5188072d7cbe2d513eec7766226f1f-675x342.png

dee6f667bc5188072d7cbe2d513eec7766226f1f-675x342.png

446 ms

2387100116c689dc31b01d668567d1e07566841c-5464x3640.jpg

2387100116c689dc31b01d668567d1e07566841c-5464x3640.jpg

437 ms

e90c4c92b2c00517d080c9ff51655eb2fcdae4cd-1084x658.jpg

e90c4c92b2c00517d080c9ff51655eb2fcdae4cd-1084x658.jpg

453 ms

9b88d8dab29fb77f58788c38bca3622b32d36b8c-964x616.webp

9b88d8dab29fb77f58788c38bca3622b32d36b8c-964x616.webp

571 ms

main.js

main.js

61 ms

Accessibility Review

jasper.io accessibility score

72

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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

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

jasper.io 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

jasper.io SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Jasper.io 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 Jasper.io 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

jasper.io

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