HubSpot COS(CMS), meet Lighthouse

Dear HubSpot Product Team, have you started to use any recommendations from Google’s new Lighthouse extension (BETA).

My website results (hosted on the COS) were less than optimal. Though I don’t feel many of the problems and I’m (fairly) certain my visitors aren’t having problems either it would be cool to know how much of the HubSpot platform will start adjusting to the recommended improvements from this and other tools.

PS. I love HubSpot so I’m really not complaining at all! BUT, I would love to see an improvement to the platform. Let’s get my score from 45 to 90 in the next 9 months!

I pasted some of the copy from the “BEST PRACTICES” section below.

Best Practices

We’ve compiled some recommendations for modernizing your web app and avoiding performance pitfalls. These audits do not affect your score but are worth a look.

Using modern offline features

Using modern protocols

• Uses HTTPS
• Pass
• Uses HTTP/2 for its own resources: 35 requests were not handled over h2
• Fail

Using modern CSS features

• Avoids old CSS flexbox << FAIL

Using modern JavaScript features

Avoiding APIs that harm the user experience

• Avoids document.write()
• Pass
• Opens external anchors using rel=”noopener”
• URLs
• Avoids requesting the geolocation permission on page load
• Pass
• Avoids requesting the notification permission on page load
• Pass

Avoiding deprecated APIs and browser interventions

Accessibility

• Element aria-* attributes are allowed for this role
• Pass
• Elements with ARIA roles have the required aria-* attributes
• Pass
• Element aria-* attributes are valid and not misspelled or non-existent.
• Pass
• Element aria-* attributes have valid values
• Pass
• Background and foreground colors have a sufficient contrast ratio
• Fail
• 10 elements fail this test
• Every image element has an alt attribute
• Fail
• 1 element failed this test
• Every form element has a label
• Pass
• No element has a tabindex attribute greater than 0
• Pass

Other

• Manifest’s short_name won't be truncated when displayed on homescreen
• Fail
• Manifest’s display property is set
• Fail

Performance

These encapsulate your app’s performance.

• Unused CSS rules: Potential savings of 92 KB (~470ms)
• Fail
• View details
• Unoptimized images: Potential savings of 536 KB (~2,770ms)
• Pass
• View details
• Oversized Images: Potential savings of 23 KB (~120ms)
• Pass
• View details
• Critical Request Chains: 26
• Fail
• Longest chain: 11,883.7ms over 1 requests, totalling 3.79KB
• View critical network waterfall
• Render-blocking Stylesheets: 3 resources delayed first paint by 74ms
• Fail
• View details
• Render-blocking scripts: 2 resources delayed first paint by 85ms
• Fail
• (99/100) Avoids enormous network payloads: Total size was 1,872 KB (target: 1,600 KB)
• (100/100)Avoids an excessive DOM size: 806 nodes (target: 1,500 nodes)
• User Timing marks and measures: 2
• Pass