Tools & Wizards About Us
peregrine.ai screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

peregrine.ai

AI-powered vision, for smarter cameras

Page Load Speed

5.9 sec in total

First Response

558 ms

Resources Loaded

4.9 sec

Page Rendered

425 ms

peregrine.ai screenshot

About Website

Click here to check amazing Peregrine content. Otherwise, check out these important facts you probably never knew about peregrine.ai

We build highly efficient perception systems to power millions of smart cameras around the globe - delivering unparalleled contextual awareness in mobility.

Visit peregrine.ai

Key Findings

We analyzed Peregrine.ai page load time and found that the first response time was 558 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

peregrine.ai performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value1.044

2/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

peregrine.ai

558 ms

script.js

44 ms

main.min.css

114 ms

css

87 ms

download.css

223 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 88% of them (46 requests) were addressed to the original Peregrine.ai, 4% (2 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Cdn-cookieyes.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Peregrine.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (24%)

Content Size

5.7 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peregrine.ai main page is 5.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. 40% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 236.3 kB

  • Original 274.6 kB
  • After minification 271.1 kB
  • After compression 38.3 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 236.3 kB or 86% of the original size.

Image Optimization

-10%

Potential reduce by 466.9 kB

  • Original 4.5 MB
  • After minification 4.0 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. Peregrine images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 314.7 kB

  • Original 492.3 kB
  • After minification 491.5 kB
  • After compression 177.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 314.7 kB or 64% of the original size.

CSS Optimization

-77%

Potential reduce by 326.6 kB

  • Original 423.0 kB
  • After minification 407.8 kB
  • After compression 96.4 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. Peregrine.ai needs all CSS files to be minified and compressed as it can save up to 326.6 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (76%)

Requests Now

50

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peregrine.ai

peregrine.ai

558 ms

script.js

script.js

44 ms

main.min.css

main.min.css

114 ms

css

css

87 ms

download.css

download.css

223 ms

dashicons.min.css

dashicons.min.css

471 ms

all.css

all.css

499 ms

frontend.min.css

frontend.min.css

495 ms

widget-image.min.css

widget-image.min.css

316 ms

widget-heading.min.css

widget-heading.min.css

304 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

332 ms

widget-icon-list.min.css

widget-icon-list.min.css

413 ms

animations.min.css

animations.min.css

515 ms

swiper.min.css

swiper.min.css

438 ms

e-swiper.min.css

e-swiper.min.css

517 ms

popup.min.css

popup.min.css

539 ms

all.min.css

all.min.css

654 ms

v4-shims.min.css

v4-shims.min.css

695 ms

css

css

81 ms

wca.min.js

wca.min.js

598 ms

jquery.min.js

jquery.min.js

710 ms

jquery-migrate.min.js

jquery-migrate.min.js

627 ms

v4-shims.min.js

v4-shims.min.js

639 ms

js

js

102 ms

widget-text-editor.min.css

widget-text-editor.min.css

699 ms

widget-icon-box.min.css

widget-icon-box.min.css

793 ms

frontend.min.js

frontend.min.js

834 ms

media-query.js

media-query.js

800 ms

download.js

download.js

803 ms

googlesitekit-consent-mode-3d6495dceaebc28bcca3.js

googlesitekit-consent-mode-3d6495dceaebc28bcca3.js

891 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

905 ms

wp-consent-api.min.js

wp-consent-api.min.js

831 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

848 ms

webpack.runtime.min.js

webpack.runtime.min.js

898 ms

frontend-modules.min.js

frontend-modules.min.js

1028 ms

hooks.min.js

hooks.min.js

937 ms

i18n.min.js

i18n.min.js

950 ms

frontend.min.js

frontend.min.js

1084 ms

core.min.js

core.min.js

1005 ms

frontend.min.js

frontend.min.js

1022 ms

elements-handlers.min.js

elements-handlers.min.js

1051 ms

log

log

412 ms

Logo-Peregrine-midnight.svg

Logo-Peregrine-midnight.svg

318 ms

Heroimage-2.jpg

Heroimage-2.jpg

753 ms

vt-homepage-tiny-e1704270474774-1024x633.jpg

vt-homepage-tiny-e1704270474774-1024x633.jpg

395 ms

image-3-1024x757.jpg

image-3-1024x757.jpg

617 ms

image-car-blur.jpg

image-car-blur.jpg

509 ms

image-face-blur-1.jpg

image-face-blur-1.jpg

530 ms

logo-icon-midnight.svg

logo-icon-midnight.svg

450 ms

ERDF.png

ERDF.png

499 ms

Vision-AI-whitepaper-peregrine-ai.png

Vision-AI-whitepaper-peregrine-ai.png

1091 ms

font

font

19 ms

Accessibility Review

peregrine.ai 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-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

peregrine.ai 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

SEO Factors

peregrine.ai SEO score

79

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

High

Image elements do not have [alt] attributes

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 Peregrine.ai 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 Peregrine.ai 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

peregrine.ai

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