Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

plungepad.io

Plunge Pad | The first and fairest launchpad built on Arbitrum

Page Load Speed

3.6 sec in total

First Response

93 ms

Resources Loaded

2.5 sec

Page Rendered

953 ms

plungepad.io screenshot

About Website

Welcome to plungepad.io homepage info - get ready to check Plunge Pad best content for Ukraine right away, or after learning these important things about plungepad.io

Plunge Pad is the first launchpad dedicated to launching projects on Arbitrum. It’s a platform that grants every holder of our exclusive token access to pre-sales of projects selected for our launchpa...

Visit plungepad.io

Key Findings

We analyzed Plungepad.io page load time and found that the first response time was 93 ms and then it took 3.5 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

plungepad.io performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value51.2 s

0/100

10%

TBT (Total Blocking Time)

Value53,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value103.4 s

0/100

10%

Network Requests Diagram

plungepad.io

93 ms

plungepad.io

283 ms

css2

122 ms

polyfill-8b58833c1f94fa440bc7.js

942 ms

component---src-pages-index-js-e63fff465fb111deba2c.js

829 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Plungepad.io, 9% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Plungepad.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.8 kB (15%)

Content Size

1.7 MB

After Optimization

1.5 MB

In fact, the total size of Plungepad.io main page is 1.7 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. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-43%

Potential reduce by 140.7 kB

  • Original 328.8 kB
  • After minification 328.7 kB
  • After compression 188.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 140.7 kB or 43% of the original size.

Image Optimization

-10%

Potential reduce by 130.0 kB

  • Original 1.4 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. Plunge Pad images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 176 B

  • Original 53.5 kB
  • After minification 53.4 kB
  • After compression 53.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.

Requests Breakdown

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

Requests Now

40

After Optimization

29

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

Accessibility Review

plungepad.io accessibility score

87

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

plungepad.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

plungepad.io SEO score

86

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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