Tools & Wizards About Us

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

arize.com

AI Observability & LLM Evaluation Platform | ML Model Monitoring & ML Infrastructure

Page Load Speed

2.9 sec in total

First Response

199 ms

Resources Loaded

1.1 sec

Page Rendered

1.7 sec

About Website

Click here to check amazing Arize content for United States. Otherwise, check out these important facts you probably never knew about arize.com

Increase model velocity and improve AI outcomes with Arize's AI and ML observability platform. Discover issues, diagnose problems, and improve performance.

Visit arize.com

Key Findings

We analyzed Arize.com page load time and found that the first response time was 199 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

arize.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.417

23/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

arize.com

199 ms

arize.com

323 ms

tribe-events-pro-mini-calendar-block.min.css

38 ms

search-forms.css

133 ms

am_https-fonts-googleapis-com-css2familymontserratitalwght030004000500060007001400displayswap.css

140 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 93% of them (66 requests) were addressed to the original Arize.com, 4% (3 requests) were made to Player.vimeo.com and 3% (2 requests) were made to I.vimeocdn.com. The less responsive or slowest element that took the longest time to load (342 ms) belongs to the original domain Arize.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.0 kB (65%)

Content Size

439.9 kB

After Optimization

151.9 kB

  • HTML
  • Images

In fact, the total size of Arize.com main page is 439.9 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. 30% of websites need less resources to load. HTML takes 256.6 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 233.0 kB

  • Original 256.6 kB
  • After minification 159.2 kB
  • After compression 23.6 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 97.4 kB, which is 38% 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 233.0 kB or 91% of the original size.

Image Optimization

-30%

Potential reduce by 55.0 kB

  • Original 183.3 kB
  • After minification 128.3 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, Arize needs image optimization as it can save up to 55.0 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 15 (22%)

Requests Now

69

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

arize.com accessibility score

85

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

arize.com 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

Missing source maps for large first-party JavaScript

SEO Factors

arize.com SEO score

86

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

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