Access 1inch.io. Top DeFi Products & Solutions for Web3

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value2,420 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.483

17/100

15%

TTI (Time to Interactive)

Value24.5 s

0/100

10%

1inch.io

444 ms

ca0e0f2cca0f293a.css

347 ms

91aa673899b7b46d.css

354 ms

441e33252950bc1d.css

38 ms

polyfills-c67a75d1b6f99dc8.js

387 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that all of those requests were addressed to 1inch.io and no external sources were called. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain 1inch.io.

Content Size

4.1 MB

After Optimization

120.9 kB

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

HTML Optimization

-75%

Potential reduce by 228.8 kB

Original 305.3 kB
After minification 305.3 kB
After compression 76.5 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 228.8 kB or 75% of the original size.

Image Optimization

-99%

Potential reduce by 3.7 MB

Original 3.8 MB
After minification 44.4 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, 1 Inch needs image optimization as it can save up to 3.7 MB or 99% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Now

111

After Optimization

The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 Inch. 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 Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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/).

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 1inch.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 1inch.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 1 Inch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: