Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

zpr.io

URL Shortener by Zapier Integrations | Connect Your Apps with Zapier

Page Load Speed

2 sec in total

First Response

12 ms

Resources Loaded

1.3 sec

Page Rendered

680 ms

zpr.io screenshot

About Website

Welcome to zpr.io homepage info - get ready to check Zpr best content for Japan right away, or after learning these important things about zpr.io

Instantly connect URL Shortener by Zapier with the apps you use everyday. URL Shortener by Zapier integrates with 6,000 other apps on Zapier - it's the easiest way to automate your work.

Visit zpr.io

Key Findings

We analyzed Zpr.io page load time and found that the first response time was 12 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

zpr.io performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value8,210 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

zpr.io

12 ms

integrations

70 ms

css2

39 ms

polyfills-60cf798e4b70d8c195e1.js

18 ms

main-a97ccb51c97103f7757e.js

22 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Zpr.io, 56% (37 requests) were made to Zapier-images.imgix.net and 38% (25 requests) were made to Cdn.zapier.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Cdn.zapier.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 871.8 kB (52%)

Content Size

1.7 MB

After Optimization

803.8 kB

In fact, the total size of Zpr.io main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 983.6 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 869.9 kB

  • Original 983.6 kB
  • After minification 982.7 kB
  • After compression 113.7 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 869.9 kB or 88% of the original size.

Image Optimization

-4%

Potential reduce by 1.9 kB

  • Original 51.4 kB
  • After minification 49.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. Zpr images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 28 B

  • Original 640.6 kB
  • After minification 640.6 kB
  • After compression 640.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.

Requests Breakdown

Number of requests can be reduced by 31 (48%)

Requests Now

64

After Optimization

33

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

Accessibility Review

zpr.io 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

High

ARIA IDs are not unique

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

Best Practices

zpr.io 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

zpr.io SEO score

84

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

High

Tap targets are not sized appropriately

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