Tools & Wizards About Us
pi.exchange screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 53% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pi.exchange

PI.EXCHANGE | Predictive Analytics Platform

Page Load Speed

4.2 sec in total

First Response

45 ms

Resources Loaded

2.8 sec

Page Rendered

1.3 sec

pi.exchange screenshot

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

Key Findings

We analyzed Pi.exchange page load time and found that the first response time was 45 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

pi.exchange performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value2,790 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

pi.exchange

45 ms

www.pi.exchange

858 ms

jquery-1.7.1.js

47 ms

aos.css

76 ms

main.min.css

243 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 61% of them (59 requests) were addressed to the original Pi.exchange, 6% (6 requests) were made to No-cache.hubspot.com and 2% (2 requests) were made to Q.quora.com. The less responsive or slowest element that took the longest time to load (921 ms) belongs to the original domain Pi.exchange.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.7 kB (21%)

Content Size

723.4 kB

After Optimization

571.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pi.exchange main page is 723.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 404.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 136.4 kB

  • Original 160.4 kB
  • After minification 140.4 kB
  • After compression 24.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. This page needs HTML code to be minified as it can gain 20.0 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 136.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 3.2 kB

  • Original 404.7 kB
  • After minification 401.5 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. PI images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 6.3 kB

  • Original 130.9 kB
  • After minification 130.9 kB
  • After compression 124.6 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

-21%

Potential reduce by 5.9 kB

  • Original 27.4 kB
  • After minification 27.4 kB
  • After compression 21.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. Pi.exchange needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (47%)

Requests Now

90

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 90 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 30 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pi.exchange

pi.exchange

45 ms

www.pi.exchange

www.pi.exchange

858 ms

jquery-1.7.1.js

jquery-1.7.1.js

47 ms

aos.css

aos.css

76 ms

main.min.css

main.min.css

243 ms

module_-35056501883_Video.min.css

module_-35056501883_Video.min.css

86 ms

module_140934023698_Card_Grid_Hover.min.css

module_140934023698_Card_Grid_Hover.min.css

236 ms

module_79649866382_Taras_Testimonial_Slider.min.css

module_79649866382_Taras_Testimonial_Slider.min.css

732 ms

module_106583928890_Simple_Card_Push_Bounce.min.css

module_106583928890_Simple_Card_Push_Bounce.min.css

61 ms

js

js

116 ms

current.js

current.js

87 ms

slick.min.js

slick.min.js

69 ms

slick.min.css

slick.min.css

76 ms

embed.js

embed.js

72 ms

aos.js

aos.js

81 ms

main.min.js

main.min.js

232 ms

helper.min.js

helper.min.js

79 ms

child.min.js

child.min.js

278 ms

project.js

project.js

111 ms

module_105763646101_Navbar_with_Menu.min.js

module_105763646101_Navbar_with_Menu.min.js

298 ms

module_-35056501883_Video.min.js

module_-35056501883_Video.min.js

98 ms

loader.js

loader.js

81 ms

module_79649866382_Taras_Testimonial_Slider.min.js

module_79649866382_Taras_Testimonial_Slider.min.js

408 ms

v2.js

v2.js

274 ms

3917840.js

3917840.js

278 ms

index.js

index.js

294 ms

gtm.js

gtm.js

171 ms

7e69a8dd-b9a5-483d-bf8b-47268c672fe5.png

7e69a8dd-b9a5-483d-bf8b-47268c672fe5.png

245 ms

top-post-badge.svg

top-post-badge.svg

447 ms

PI.EXCHANGE_LOGO_COMBO_20190819_FullColour-1.png

PI.EXCHANGE_LOGO_COMBO_20190819_FullColour-1.png

150 ms

13.svg

13.svg

286 ms

12.svg

12.svg

149 ms

14.svg

14.svg

244 ms

data_security_privacy.svg

data_security_privacy.svg

239 ms

templated%20solutions.svg

templated%20solutions.svg

155 ms

20.svg

20.svg

453 ms

22.svg

22.svg

241 ms

21.svg

21.svg

244 ms

Join%20slack.svg

Join%20slack.svg

427 ms

calendar.svg

calendar.svg

522 ms

19.svg

19.svg

455 ms

23.svg

23.svg

510 ms

homepage%20background.jpg

homepage%20background.jpg

524 ms

Hero%20AIAE%20homepage.png

Hero%20AIAE%20homepage.png

508 ms

microsoft-azure-homepage-logo.svg

microsoft-azure-homepage-logo.svg

520 ms

AWS.svg

AWS.svg

523 ms

Google-cloud-homepage-logo.svg

Google-cloud-homepage-logo.svg

627 ms

huawei-cloud-homepage-logo.svg

huawei-cloud-homepage-logo.svg

603 ms

intel-homepage-logo.svg

intel-homepage-logo.svg

630 ms

NVIDIA.svg

NVIDIA.svg

629 ms

Bespin-global-homepage-logo.svg

Bespin-global-homepage-logo.svg

597 ms

Intersystems.svg

Intersystems.svg

606 ms

Prepare%20and%20analyze%20data.png

Prepare%20and%20analyze%20data.png

730 ms

Build%20models%20homepage.png

Build%20models%20homepage.png

729 ms

Generate%20and%20export%20predictions%20home%20page.png

Generate%20and%20export%20predictions%20home%20page.png

724 ms

Marketers-sales.jpg

Marketers-sales.jpg

715 ms

Product-builders.jpg

Product-builders.jpg

716 ms

Business-data-analysts.jpg

Business-data-analysts.jpg

712 ms

Data-scientists.jpg

Data-scientists.jpg

767 ms

watch_demo.jpg

watch_demo.jpg

747 ms

contact_us-2.jpg

contact_us-2.jpg

754 ms

book_a_meeting.jpg

book_a_meeting.jpg

752 ms

Untitled%20design%20(32)-2.png

Untitled%20design%20(32)-2.png

760 ms

beba0c76-1e46-43dd-a009-0462f19b9d51.png

beba0c76-1e46-43dd-a009-0462f19b9d51.png

235 ms

11167ae6-032e-4cb7-8189-87210f4cbe7c.png

11167ae6-032e-4cb7-8189-87210f4cbe7c.png

280 ms

58b9f62f-bdab-45c7-80e2-7aca05bf1062.png

58b9f62f-bdab-45c7-80e2-7aca05bf1062.png

280 ms

f1f1aeae-22be-4f01-a9e1-fae13db30965.png

f1f1aeae-22be-4f01-a9e1-fae13db30965.png

425 ms

02432a86-b047-4a45-a92f-d6d394fe93a0.png

02432a86-b047-4a45-a92f-d6d394fe93a0.png

426 ms

regular.woff

regular.woff

644 ms

300.woff

300.woff

685 ms

500.woff

500.woff

802 ms

regular.woff

regular.woff

921 ms

700.woff

700.woff

815 ms

landing

landing

374 ms

insight.min.js

insight.min.js

355 ms

uwt.js

uwt.js

323 ms

qevents.js

qevents.js

367 ms

pixel

pixel

267 ms

hotjar-2037943.js

hotjar-2037943.js

423 ms

analytics.js

analytics.js

262 ms

pixel.js

pixel.js

309 ms

homepage-section-3-bg.svg

homepage-section-3-bg.svg

617 ms

header%20purple%20with%20wave%20%285%29.svg

header%20purple%20with%20wave%20%285%29.svg

548 ms

Footer-2.svg

Footer-2.svg

595 ms

3917840.js

3917840.js

287 ms

conversations-embed.js

conversations-embed.js

253 ms

web-interactives-embed.js

web-interactives-embed.js

280 ms

3917840.js

3917840.js

307 ms

fb.js

fb.js

279 ms

leadflows.js

leadflows.js

250 ms

collect

collect

63 ms

rp.gif

rp.gif

181 ms

t2_6xg0f9e0_telemetry

t2_6xg0f9e0_telemetry

179 ms

modules.fd7a1c20a85f7a95e5ff.js

modules.fd7a1c20a85f7a95e5ff.js

77 ms

adsct

adsct

215 ms

adsct

adsct

222 ms

pixel

pixel

8 ms

Accessibility Review

pi.exchange accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

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

High

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

Best Practices

pi.exchange best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pi.exchange SEO score

93

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

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 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: