Tools & Wizards About Us
pactly.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pactly.com

Pactly: Contract negotiation software for legal teams

Page Load Speed

3.5 sec in total

First Response

28 ms

Resources Loaded

1.3 sec

Page Rendered

2.1 sec

pactly.com screenshot

About Website

Visit pactly.com now to see the best up-to-date Pactly content and also check out these interesting facts you probably never knew about pactly.com

An all-in-one contract negotiation platform that helps your legal team draft, review, negotiate and manage your contracts.

Visit pactly.com

Key Findings

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

Performance Metrics

pactly.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

pactly.com

28 ms

www.pactly.com

127 ms

main.css

30 ms

theme-overrides.min.css

39 ms

module_70965164925_single-image.min.css

38 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 76% of them (64 requests) were addressed to the original Pactly.com, 6% (5 requests) were made to Cdn.jsdelivr.net and 6% (5 requests) were made to 21706293.fs1.hubspotusercontent-na1.net. The less responsive or slowest element that took the longest time to load (793 ms) belongs to the original domain Pactly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.0 kB (29%)

Content Size

356.0 kB

After Optimization

251.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pactly.com main page is 356.0 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. 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. Javascripts take 113.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 87.5 kB

  • Original 103.6 kB
  • After minification 93.3 kB
  • After compression 16.1 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 87.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 112.8 kB
  • After minification 112.8 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. Pactly images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 7.3 kB

  • Original 113.0 kB
  • After minification 113.0 kB
  • After compression 105.7 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

-35%

Potential reduce by 9.3 kB

  • Original 26.6 kB
  • After minification 26.6 kB
  • After compression 17.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. Pactly.com needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (37%)

Requests Now

75

After Optimization

47

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pactly.com

pactly.com

28 ms

www.pactly.com

www.pactly.com

127 ms

main.css

main.css

30 ms

theme-overrides.min.css

theme-overrides.min.css

39 ms

module_70965164925_single-image.min.css

module_70965164925_single-image.min.css

38 ms

project.css

project.css

47 ms

legacyGalleryModule.css

legacyGalleryModule.css

45 ms

module_70968923247_socials-text.min.css

module_70968923247_socials-text.min.css

36 ms

homepage.css

homepage.css

47 ms

bootstrap.min.css

bootstrap.min.css

22 ms

bootstrap-icons.css

bootstrap-icons.css

25 ms

aos.js

aos.js

41 ms

aos.css

aos.css

54 ms

embed.js

embed.js

56 ms

jquery.min.js

jquery.min.js

57 ms

vendors.min.js

vendors.min.js

57 ms

app.min.js

app.min.js

67 ms

project.js

project.js

66 ms

jquery-1.11.2.js

jquery-1.11.2.js

70 ms

project.js

project.js

75 ms

21706293.js

21706293.js

513 ms

index.js

index.js

73 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

21 ms

typed.js@2.0.12

typed.js@2.0.12

21 ms

redesign.css

redesign.css

74 ms

global_styles.min.css

global_styles.min.css

59 ms

floating-elements.svg

floating-elements.svg

390 ms

diffuser.js

diffuser.js

397 ms

email.svg

email.svg

191 ms

calendar.svg

calendar.svg

191 ms

slider-bg-elements-1.svg

slider-bg-elements-1.svg

202 ms

slider-bg-elements-2.svg

slider-bg-elements-2.svg

359 ms

pactly-logo-1.svg

pactly-logo-1.svg

175 ms

button-arrow.svg

button-arrow.svg

176 ms

hero-illustration.svg

hero-illustration.svg

202 ms

wavemaker-logo.svg

wavemaker-logo.svg

370 ms

nus-logo.svg

nus-logo.svg

195 ms

virtuos-logo.svg

virtuos-logo.svg

173 ms

dashboard-word-sidebar-5.svg

dashboard-word-sidebar-5.svg

241 ms

Flexible%2C%20easy%20to%20fill-in%20questionnaires.svg

Flexible%2C%20easy%20to%20fill-in%20questionnaires.svg

427 ms

Enable%20business%20to%20self-serve.svg

Enable%20business%20to%20self-serve.svg

238 ms

consistent-draft-contracts-1.svg

consistent-draft-contracts-1.svg

302 ms

feature-2.svg

feature-2.svg

285 ms

Review%20contracts%20accurately.svg

Review%20contracts%20accurately.svg

258 ms

Capture%20institutional%20knowledge.svg

Capture%20institutional%20knowledge.svg

283 ms

Painless%20document%20versioning.svg

Painless%20document%20versioning.svg

316 ms

Never%20forget%20key%20events.svg

Never%20forget%20key%20events.svg

318 ms

homepage-feature-3a.svg

homepage-feature-3a.svg

319 ms

virtuos-white.svg

virtuos-white.svg

452 ms

testimonial-picture-1.png

testimonial-picture-1.png

334 ms

wavemaker-white.svg

wavemaker-white.svg

330 ms

megan-hau.png

megan-hau.png

337 ms

icon-1.svg

icon-1.svg

335 ms

icon-2.svg

icon-2.svg

337 ms

icon-3.svg

icon-3.svg

339 ms

icon-4.svg

icon-4.svg

511 ms

icon-6.svg

icon-6.svg

350 ms

icon-5.svg

icon-5.svg

341 ms

icon-7.svg

icon-7.svg

370 ms

icon-8.svg

icon-8.svg

375 ms

icon-9.svg

icon-9.svg

386 ms

half-the-story.svg

half-the-story.svg

396 ms

equally-important.svg

equally-important.svg

398 ms

contract-timeline-mobile.svg

contract-timeline-mobile.svg

416 ms

contract-lifecycle-v2-1.svg

contract-lifecycle-v2-1.svg

686 ms

button-arrow.svg

button-arrow.svg

793 ms

cta_illustration-1.svg

cta_illustration-1.svg

435 ms

bootstrap-icons.woff

bootstrap-icons.woff

21 ms

21706293.js

21706293.js

147 ms

banner.js

banner.js

194 ms

leadflows.js

leadflows.js

99 ms

conversations-embed.js

conversations-embed.js

102 ms

fb.js

fb.js

101 ms

300.woff

300.woff

565 ms

regular.woff

regular.woff

306 ms

500.woff

500.woff

335 ms

600.woff

600.woff

326 ms

slick.woff

slick.woff

351 ms

logo-white.svg

logo-white.svg

310 ms

Pactly%20Whitepaper%20Adopting%20a%20digital%20contract%20lifecycle%20management%20tool-images-0.jpg

Pactly%20Whitepaper%20Adopting%20a%20digital%20contract%20lifecycle%20management%20tool-images-0.jpg

305 ms

Pactly%20Whitepaper%20Adopting%20a%20digital%20contract%20lifecycle%20management%20tool-images-4-1.jpg

Pactly%20Whitepaper%20Adopting%20a%20digital%20contract%20lifecycle%20management%20tool-images-4-1.jpg

306 ms

Pactly%20Whitepaper%20Adopting%20a%20digital%20contract%20lifecycle%20management%20tool-images-5-1.jpg

Pactly%20Whitepaper%20Adopting%20a%20digital%20contract%20lifecycle%20management%20tool-images-5-1.jpg

282 ms

ajax-loader.gif

ajax-loader.gif

272 ms

prism.app-us1.com

prism.app-us1.com

117 ms

Accessibility Review

pactly.com accessibility score

80

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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

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

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

Links do not have a discernible name

Best Practices

pactly.com best practices score

75

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

Page has valid source maps

SEO Factors

pactly.com SEO score

93

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

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

pactly.com

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