Artlist.io Performance Analysis
I analyzed artlist.io and toolkit.artlist.io using Lighthouse, Chrome DevTools, and HAR file analysis to identify performance bottlenecks and optimization opportunities.
Data collected on January 25, 2026 • This is an independent technical audit, not affiliated with Artlist
Key Findings
Critical36
out of 100 (poor)
8.5 s
should be < 2.5s
13.4 MB
excessive bundle size
431
network requests on load
Summary
- •Desktop users wait 8.8 s before the page becomes interactive - users on slower connections likely abandon
- •13.4 MB of JavaScript loaded - most users only need a fraction of this on initial load
- •16 third-party services detected - analytics overlap (Hotjar + Clarity + Segment) adds unnecessary overhead
- •Good foundation: Next.js App Router, modern image formats (AVIF), proper SEO score (91/100)
Lighthouse Scores
https://artlist.ioPerformance
36
Accessibility
80
Best Practices
96
SEO
91
Core Web Vitals (desktop)
1.8 s
First Contentful Paint
8.5 s
Largest Contentful Paint
250 ms
Total Blocking Time
0.277
Cumulative Layout Shift
4.8 s
Speed Index
8.8 s
Time to Interactive
What I Would Fix
Prioritized optimization opportunities based on impact
Reduce JavaScript bundle size
javascript14MB of JavaScript is loaded on initial page load. Implement aggressive code splitting, lazy loading for below-fold components, and tree shaking to reduce initial bundle by 50-70%.
Potential 7-10MB reduction
Consolidate analytics tools
third-partyRunning Hotjar, Clarity, Segment, and GTM simultaneously creates significant overhead. Hotjar and Clarity have overlapping functionality - consider keeping only one.
~500KB + reduced CPU overhead
Defer non-critical third-party scripts
third-party16 third-party services load during page initialization. Defer marketing pixels (LinkedIn, Snapchat, Bing) until after user interaction.
Optimize LCP element
renderingLCP of 8.5s on desktop indicates the main content loads too late. Add fetchpriority="high" to hero images and preload critical assets.
Target: < 2.5s LCP
Fix CLS issues
renderingCLS of 0.277 on desktop exceeds the 0.1 threshold. Reserve space for images and dynamic content to prevent layout shifts.
Network Analysis
431 requests · 17.2 MB totalResource Breakdown
Detected Tech Stack
Detected via network analysis, script patterns, and response headers
Third-Party Services
(16 detected)Google Tag Manager
googletagmanager.com
Tag management & analytics orchestration
Google Analytics
analytics.google.com
Web analytics
Segment
cdn.segment.com
Customer data platform
Hotjar
hotjar.com
Heatmaps & session recordings
Microsoft Clarity
clarity.ms
Behavioral analytics
Sentry
sentry.io
Error monitoring & reporting
DataDog
datadoghq.com
Application performance monitoring
Split.io
split.io
Feature flag management
Braze
braze.eu
Customer engagement platform
Google Ads
googleads.g.doubleclick.net
Advertising & remarketing
LinkedIn Ads
ads.linkedin.com
Advertising pixel
Snapchat Ads
snapchat.com
Advertising pixel
Bing Ads
bat.bing.com
Advertising pixel
Imgix
imgix.net
Image CDN & optimization
Font Awesome
fontawesome.com
Icon font library
Cookie Script
cookie-script.com
Cookie consent management
I Can Implement These Optimizations
As a senior frontend engineer specializing in Next.js and performance optimization, I have hands-on experience reducing bundle sizes by 60%+, improving Core Web Vitals, and implementing efficient third-party script loading strategies.