Tools & Wizards About Us
pacaso.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

pacaso.com

Luxury vacation home co-ownership | Pacaso

Page Load Speed

1.9 sec in total

First Response

76 ms

Resources Loaded

994 ms

Page Rendered

829 ms

pacaso.com screenshot

About Website

Visit pacaso.com now to see the best up-to-date Pacaso content for United States and also check out these interesting facts you probably never knew about pacaso.com

Pacaso offers luxury vacation homes for co-ownership. It's the modern way to buy and own a vacation home.

Visit pacaso.com

Key Findings

We analyzed Pacaso.com page load time and found that the first response time was 76 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

pacaso.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value7,160 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

Network Requests Diagram

www.pacaso.com

76 ms

ab93e7af6cab8260.css

32 ms

e0eb31ac5e2e2ae6.css

47 ms

7141e829162fc40f.css

49 ms

polyfills-c67a75d1b6f99dc8.js

811 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 33% of them (19 requests) were addressed to the original Pacaso.com, 40% (23 requests) were made to Images.ctfassets.net and 12% (7 requests) were made to D2lek8u79qswmc.cloudfront.net. The less responsive or slowest element that took the longest time to load (811 ms) belongs to the original domain Pacaso.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 530.7 kB (24%)

Content Size

2.2 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pacaso.com main page is 2.2 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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 530.1 kB

  • Original 621.0 kB
  • After minification 620.9 kB
  • After compression 90.8 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 530.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 119 B

  • Original 507.0 kB
  • After minification 506.9 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. Pacaso images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 386 B

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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

-0%

Potential reduce by 49 B

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 52.9 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. Pacaso.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (35%)

Requests Now

49

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pacaso.com

www.pacaso.com

76 ms

ab93e7af6cab8260.css

ab93e7af6cab8260.css

32 ms

e0eb31ac5e2e2ae6.css

e0eb31ac5e2e2ae6.css

47 ms

7141e829162fc40f.css

7141e829162fc40f.css

49 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

811 ms

2866.8708814b966db365.js

2866.8708814b966db365.js

49 ms

webpack-52321e263091af8d.js

webpack-52321e263091af8d.js

79 ms

framework-2114f3935436c3d0.js

framework-2114f3935436c3d0.js

48 ms

main-0a2bc8b75ca9fe0c.js

main-0a2bc8b75ca9fe0c.js

49 ms

_app-39bba2adda1b3d84.js

_app-39bba2adda1b3d84.js

170 ms

2897-5bae47606db85e1a.js

2897-5bae47606db85e1a.js

79 ms

5990-f72cd7f891718952.js

5990-f72cd7f891718952.js

78 ms

5305-7f5191cb87d1e983.js

5305-7f5191cb87d1e983.js

88 ms

2139-c32d522002800f9a.js

2139-c32d522002800f9a.js

99 ms

1473-6774bfb03b9fa54a.js

1473-6774bfb03b9fa54a.js

99 ms

8949-b23a07c3d52186ad.js

8949-b23a07c3d52186ad.js

98 ms

index-963c4a1a5791089a.js

index-963c4a1a5791089a.js

98 ms

_buildManifest.js

_buildManifest.js

158 ms

_ssgManifest.js

_ssgManifest.js

163 ms

css2

css2

108 ms

Logo_Type_Light__1_.png

Logo_Type_Light__1_.png

88 ms

width:425

width:425

99 ms

width:425

width:425

82 ms

width:425

width:425

87 ms

width:425

width:425

134 ms

width:425

width:425

81 ms

width:425

width:425

86 ms

width:425

width:425

134 ms

Screen_Shot_2023-08-31_at_1.26.08_PM.png

Screen_Shot_2023-08-31_at_1.26.08_PM.png

134 ms

Find_home_Icon.svg

Find_home_Icon.svg

139 ms

icon_by.svg

icon_by.svg

138 ms

icon-family.svg

icon-family.svg

144 ms

streamline-icon-real-estate-market-house-rise_80x80.svg

streamline-icon-real-estate-market-house-rise_80x80.svg

140 ms

PacasoLifestyleShoot-105.jpg

PacasoLifestyleShoot-105.jpg

146 ms

WSJ.png

WSJ.png

147 ms

NYT.png

NYT.png

148 ms

CNBC.png

CNBC.png

150 ms

Fortune.png

Fortune.png

151 ms

Geekwire.png

Geekwire.png

168 ms

realdeal.png

realdeal.png

170 ms

Inman.png

Inman.png

148 ms

Pacaso_LogoFiles_0522_Pacaso-Logo_Icon_Light.png

Pacaso_LogoFiles_0522_Pacaso-Logo_Icon_Light.png

155 ms

apple.svg

apple.svg

158 ms

Get_It_On_Google_Play_Badge.svg

Get_It_On_Google_Play_Badge.svg

150 ms

Mediamodifier-Design_copy_3.svg

Mediamodifier-Design_copy_3.svg

155 ms

icon-linkedin.svg

icon-linkedin.svg

163 ms

Mediamodifier-Design_copy_2.svg

Mediamodifier-Design_copy_2.svg

161 ms

icon-youtube.svg

icon-youtube.svg

164 ms

icon-pinterest.svg

icon-pinterest.svg

167 ms

Logo_Type_Dark__1_.png

Logo_Type_Dark__1_.png

165 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

50 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf

78 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

99 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

100 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

99 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYMZg.ttf

100 ms

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAw.ttf

SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RUAw.ttf

8 ms

Accessibility Review

pacaso.com accessibility score

72

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pacaso.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pacaso.com SEO score

91

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

Image elements do not have [alt] attributes

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

pacaso.com

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