Access pi.exchange. PI.EXCHANGE | Predictive Analytics Platform

Report Summary

About Website

Visit pi.exchange now to see the best up-to-date PI content and also check out these interesting facts you probably never knew about pi.exchange

The AI & Analytics Engine is a predictive analytics platform that enables manufacturers, distributors and LSP's to make data-driven decisions.

Visit pi.exchange

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value5.9 s

47/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

pi.exchange

46 ms

www.pi.exchange

1282 ms

auto-blocking.js

129 ms

jquery-1.7.1.js

58 ms

aos.css

66 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 71% of them (47 requests) were addressed to the original Pi.exchange, 11% (7 requests) were made to No-cache.hubspot.com and 3% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Pi.exchange.

Content Size

1.6 MB

After Optimization

1.3 MB

In fact, the total size of Pi.exchange main page is 1.6 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 294.5 kB

Original 341.5 kB
After minification 322.4 kB
After compression 47.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 294.5 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 8.5 kB

Original 1.1 MB
After minification 1.1 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. PI images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 8.1 kB

Original 100.0 kB
After minification 100.0 kB
After compression 91.9 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

-4%

Potential reduce by 17 B

Original 408 B
After minification 408 B
After compression 391 B

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. Pi.exchange has all CSS files already compressed.

Requests Now

After Optimization

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

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

Links do not have a discernible name

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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 Pi.exchange 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 Pi.exchange 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

pi.exchange

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

Report Summary

Performance

Accessibility

Best Practices

SEO

PI.EXCHANGE | Predictive Analytics Platform

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)