Poor Lighthouse score is negatively impacting SEO.

[nearestnabors]

Both our Arize and Phoenix docs are having performance issues as documented in the attached Lighthouse report. We're getting dinged by google on LCP, and a commercial review has revealed this is no good for our SEO.

As these are not changes we can make on our end and are beneficial to all Mintlify customers, we are hoping this can be prioritized.

Mintlify Lighthouse score.pdf

Here are some things Mintlify can do to improve their product's lighthouse score:

Performance Issues

1. Render-Blocking CSS (Est savings: 720ms)
   Issue: 3 CSS files blocking initial render
   Files:

• css/93bac6dd9c729729.css (6.1 KiB, 710ms)
• css/6d69438450cf7bb8.css (39.1 KiB, 900ms)
• css/05d6d8fcb903870d.css (4.0 KiB, 710ms)

Request: Defer non-critical CSS or inline critical CSS

2. Unused CSS (Est savings: 33 KiB)
   Issue: css/6d69438450cf7bb8.css has 33.5 KiB unused
   Request: Implement CSS tree-shaking or purging

3. Unused JavaScript (Est savings: 487 KiB from first-party)
   Issue: Large JS bundles with unused code:

• chunks/80622-f3d....js: 130 KiB unused
• chunks/20660-c2e....js: 65 KiB unused
• chunks/50867-80e....js: 63 KiB unused
  Request: Better code splitting and tree-shaking

4. Legacy JavaScript Polyfills (Est savings: 12 KiB)
   Issue: Shipping polyfills for modern features:

• Array.prototype.at
• Array.prototype.flat
• Object.fromEntries
• Object.hasOwn
  Request: Use differential serving or remove polyfills

5. Total Blocking Time: 7,800ms
   Issue: Main thread work is 14.6 seconds

• Script Evaluation: 2,849ms
• "Other": 10,365ms
• 14 long tasks found
  Request: Break up long tasks, optimize JS execution

6. Missing Source Maps
   Issue: chunks/80622-f3d....js missing source map
   Impact: Debugging difficulty, Lighthouse can't provide detailed
   insights

7. Images Without Explicit Dimensions (CLS)
   Issue: logo/dark.svg from mintcdn.com has no width/height
   Impact: Layout shift (CLS: 0.007)
   Request: Add intrinsic dimensions to Mintlify-served images

Accessibility Issues

8. Button Without Accessible Name
   Element: button#assistant-entry-mobile
   Request: Add aria-label to the mobile assistant button

9. Missing Main Landmark
   Issue: Document lacks

   element
   Request: Add proper landmark structure

10. ARIA Hidden Contains Focusable Elements
    Element: div#chat-assistant-sheet (aria-hidden="true")
    Contains: buttons, textarea, links that are focusable
    Request: Fix focus management in the chat assistant

11. Duplicate ARIA IDs
    Elements with duplicate IDs:

• div#%F0%9F%94%80-tracing.tabs.tab-container
• li#%F0%9F%94%80-tracing.cursor-pointer

12. Low Contrast Text
    Multiple elements fail WCAG contrast requirements
    Request: Review gray-400/gray-600 text colors

13. Video Missing Captions
    Issue:

[maskoidtech-art]

Thanks for sharing such a detailed breakdown — this is a solid Lighthouse audit.

You’re absolutely right that LCP + TBT issues at this level will impact SEO, especially now that Google heavily factors Core Web Vitals into ranking signals.

Key Observations

From what you’ve shared, the main bottlenecks seem to be:

1. Render-Blocking CSS
   Multiple CSS files delaying first paint
   Especially noticeable given the ~700–900ms delays per file

Suggestion:

Inline critical CSS for above-the-fold content
Load remaining CSS asynchronously (media="print" swap or rel="preload")
2. Excessive Unused CSS & JS
~33KB unused CSS
~487KB unused JS (significant)

This suggests:

Over-bundling
Inefficient tree-shaking

Suggestion:

Enable stricter tree-shaking
Break bundles using route-based or component-level code splitting
Consider tools like webpack-bundle-analyzer to identify dead weight
3. High Total Blocking Time (7.8s)

This is the biggest concern.

14.6s main thread work is very high
Long tasks indicate heavy JS execution blocking interactivity

Suggestion:

Break long tasks using requestIdleCallback or chunked execution
Reduce hydration cost (if using React/Next-based architecture)
Defer non-critical scripts
4. Legacy Polyfills

Shipping polyfills for modern browsers is unnecessary overhead.

Suggestion:

Use differential serving (modern vs legacy bundles)
Drop polyfills for evergreen browsers
5. CLS Issues (Images)
Missing width/height → layout shifts

Fix:

Add intrinsic dimensions or use aspect-ratio containers
Accessibility Notes

Good catch here — these issues can also indirectly affect UX signals:

Missing aria-label → easy fix
No

landmark → impacts structure/navigation
Focusable elements inside aria-hidden → needs proper focus trapping
Duplicate ARIA IDs → can break assistive tech parsing
Bigger Picture (Important)

Since this is a platform-level issue (Mintlify), individual users can’t fully optimize around it.

So prioritizing:

Bundle optimization
CSS delivery strategy
JS execution reduction

…would benefit all customers at scale.

SEO Impact

Just to reinforce your point:

Poor LCP → affects rankings + UX
High TBT → lowers interaction readiness
CLS → impacts visual stability

These directly influence Core Web Vitals, which Google uses as a ranking factor.

Additional Note

For teams trying to compensate at the content level, strong technical SEO still plays a major role in visibility recovery and performance alignment:
👉 SEO Services Overview

(Not a direct fix here, but relevant when evaluating overall SEO impact alongside performance.)

Final Thoughts

This is a well-documented issue and definitely worth prioritizing.

If Mintlify can:

Reduce JS payload
Optimize CSS delivery
Improve main-thread execution

…it would likely result in immediate Lighthouse + SEO gains across all hosted docs.