Menu:

Save Test Results with a Free Account Sign Up & Save Test Result

Webpage Performance Test Result

Screenshot

Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. Overall scoring color key: (0-49 50-89 90-100).

Did you know? Lighthouse runs in Chrome and provides a great complementary analysis alongside the many browsers, devices, and locations WebPageTest offers. To see how this site performs in more environments: Start a new test

Performance 35

Lighthouse Metrics

Values are estimated and may vary.

The performance score is calculated directly from these metrics. See calculator.

First Contentful Paint Speed Index Largest Contentful Paint Time to Interactive Total Blocking Time Cumulative Layout Shift
5.1s 7.4s 14.6s 12.9s 270ms 0.002

Show audits relevant to metrics: ALL FCP LCP TBT CLS

View Tree Map

Opportunities (6)

  1. Reduce unused JavaScript

    Estimated savings 3.38 s

    Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.

    URL Transfer Size (bytes) Potential Savings (bytes)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js 333358 215619
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 367054 205994
    https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable 86927 76298
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 77992 40346
    https://www.googletagmanager.com/gtm.js?id=GTM-PZHN3VD 94368 34570
    https://www.googletagmanager.com/gtag/js?id=G-ZWG1NSHWD8&l=dataLayer&cx=c 76483 29839
    https://www.googleoptimize.com/optimize.js?id=GTM-W53X654 46919 26995
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-dialog-container.ae962bd6.js 27045 26372
  2. Eliminate render-blocking resources

    View Experiment!

    Estimated savings 2.12 s

    Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

    URL Transfer Size (bytes) Potential Savings (ms)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-dialog-container.ae962bd6.css 2619 2580
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-context-menu-container.b615361a.css 728 304
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.447f22d4.css 27915 304
  3. Use HTTP/2

    Estimated savings 1.76 s

    HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.

    URL Protocol
    https://lite-images-i.scdn.co/image/ab67706f00000002c03728d7ade82b2a614d3e78 http/1.1
    https://lite-images-i.scdn.co/image/ab67706f00000002c23af7e5cebbb289571b048d http/1.1
    https://lite-images-i.scdn.co/image/ab67706f00000002f27ffee7eaa33ff901a74c96 http/1.1
    https://lite-images-i.scdn.co/image/ab67706f000000025551996f500ba876bda73fa5 http/1.1
    https://lite-images-i.scdn.co/image/ab67706f00000002ca5a7517156021292e5663a6 http/1.1
    https://lite-images-i.scdn.co/image/ab67706f00000002abaf6c3c6a4b29f8a4565a86 http/1.1
  4. Enable text compression

    Estimated savings 0.15 s

    Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

    URL Transfer Size (bytes) Potential Savings (bytes)
    https://fastly-insights.com/api/v1/config/040e3997-282c-4275-ba9b-a406ce78b133 18329 16612
  5. Reduce unused CSS

    Estimated savings 0.15 s

    Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.

    URL Transfer Size (bytes) Potential Savings (bytes)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.447f22d4.css 27915 26929
    #onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} ... 17303 14783
  6. Avoid serving legacy JavaScript to modern browsers

    Estimated savings 0.15 s

    Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More

    URL Potential Savings (bytes)
    https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89 12356
    Location Signal
    • URL: https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89
    • Line: 20
    • Column: 1329
    @babel/plugin-transform-classes
    • URL: https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89
    • Line: 20
    • Column: 23583
    Array.prototype.filter
    • URL: https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89
    • Line: 20
    • Column: 29697
    Array.from
    • URL: https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89
    • Line: 20
    • Column: 31203
    Array.prototype.includes
    • URL: https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89
    • Line: 20
    • Column: 31447
    Array.prototype.map
    • URL: https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89
    • Line: 20
    • Column: 32242
    Array.prototype.find
    https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable 11168
    Location Signal
    • URL: https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable
    • Line: 19
    • Column: 1574
    @babel/plugin-transform-classes
    • URL: https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable
    • Line: 19
    • Column: 28564
    Array.prototype.filter
    • URL: https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable
    • Line: 19
    • Column: 34678
    Array.from
    • URL: https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable
    • Line: 19
    • Column: 36184
    Array.prototype.includes
    • URL: https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable
    • Line: 19
    • Column: 36428
    Array.prototype.map
    • URL: https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable
    • Line: 19
    • Column: 37223
    Array.prototype.find
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 7942
    Location Signal
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 777931
    Array.prototype.includes
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 783385
    Object.entries
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 783499
    Object.values
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 855149
    @babel/plugin-transform-classes
    https://open.spotifycdn.com/cdn/build/mobile-web-player/94.291eaf4d.js 7643
    Location Signal
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/94.291eaf4d.js
    • Line: 0
    • Column: 47317
    Object.entries
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/94.291eaf4d.js
    • Line: 0
    • Column: 47426
    Object.values
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 6535
    Location Signal
    • URL: https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js
    • Line: 6
    • Column: 5421
    Array.prototype.includes
    • URL: https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js
    • Line: 6
    • Column: 7241
    Array.prototype.fill
    https://pixel-static.spotify.com/sync.min.js 73
    Location Signal
    • URL: https://pixel-static.spotify.com/sync.min.js
    • Line: 0
    • Column: 2194
    @babel/plugin-transform-classes
    https://connect.facebook.net/en_US/fbevents.js 45
    Location Signal
    • URL: https://connect.facebook.net/en_US/fbevents.js
    • Line: 23
    • Column: 2302
    @babel/plugin-transform-classes

Diagnostics (10)

  1. Largest Contentful Paint image was lazily loaded

    View Experiment!

    Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.

    Element
    li > div.Card__CardFigure-sc-1o2nsas-0 > div.Card__CardFigureImageContainer-sc-1o2nsas-1 > img.mMx2LUixlnN_Fu45JpFB
  2. Serve static assets with an efficient cache policy

    14 resources found

    A long cache lifetime can speed up repeat visits to your page. Learn more.

    URL Cache TTL (ms) Transfer Size (bytes)
    https://pixel-static.spotify.com/sync.min.js 0 2059
    https://sb.scorecardresearch.com/internal-c2/default/cs.js 0 358
    https://www.facebook.com/tr/?id=1483047915331997&ev=PageView&dl=https%3A%2F%2Fopen.spotify.com%2F&rl=&if=false&ts=1671033361910&sw=1366&sh=768&v=2.9.89&r=stable&a=tmSimo-GTM-WebTemplate&ec=0&o=30&fbp=fb.1.1671033361909.1761150096&it=1671033359178&coo=false&dpo=LDU&dpoco=0&dpost=0&tm=1&exp=a1&rqm=GET 0 185
    https://p.adsymptotic.com/d/px/?_pid=10339&_psign=f79776ac7a290c8b1b2a94bd7ad5f0ce&_puuid=2ba7f1e6cb6b152123596d8669ba1ae71454b452425551d6c33b966a5c68d9cf791426b5417dce21&_pu&_expected_cookie=cc2f9394f7ea6427f4f8cbf433822b07 0 141
    https://www.facebook.com/tr/?id=1483047915331997&ev=Microdata&dl=https%3A%2F%2Fopen.spotify.com%2F&rl=&if=false&ts=1671033362413&cd[DataLayer]=%5B%5D&cd[Meta]=%7B%22title%22%3A%22Spotify%20%E2%80%93%20Mobile%20Web%20Player%22%2C%22meta%3Adescription%22%3A%22Spotify%20is%20a%20digital%20music%20service%20that%20gives%20you%20access%20to%20millions%20of%20songs.%22%7D&cd[OpenGraph]=%7B%22og%3Asite_name%22%3A%22Spotify%22%2C%22og%3Atitle%22%3A%22Spotify%20-%20Web%20Player%3A%20Music%20for%20everyone%22%2C%22og%3Adescription%22%3A%22Spotify%20is%20a%20digital%20music%20service%20that%20gives%20you%20access%20to%20millions%20of%20songs.%22%2C%22og%3Aurl%22%3A%22https%3A%2F%2Fopen.spotify.com%2F%22%2C%22og%3Aimage%22%3A%22https%3A%2F%2Fopen.spotifycdn.com%2Fcdn%2Fimages%2Fog-image.548bc4b7.png%22%2C%22og%3Atype%22%3A%22website%22%7D&cd[Schema.org]=%5B%5D&cd[JSON-LD]=%5B%5D&sw=1366&sh=768&v=2.9.89&r=stable&a=tmSimo-GTM-WebTemplate&ec=1&o=30&fbp=fb.1.1671033361909.1761150096&it=1671033359178&coo=false&dpo=LDU&dpoco=0&dpost=0&es=automatic&tm=3&exp=b2&rqm=GET 0 18
    https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable 1200000 86927
    https://connect.facebook.net/en_US/fbevents.js 1200000 28194
    https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89 1200000 20762
    https://www.google-analytics.com/analytics.js 7200000 20254
    https://s.pinimg.com/ct/core.js 7200000 1361
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 86400000 77992
    https://cdn.cookielaw.org/scripttemplates/otSDKStub.js 86400000 7698
    https://cdn.speedcurve.com/js/lux.js?id=4310329957 604800000 522
    https://s.pinimg.com/ct/lib/main.9a94ee76.js 1209600000 20997
  3. Registers an unload listener

    The unload event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use pagehide or visibilitychange events instead. Learn more

    Source
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 181694
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 61400
  4. Avoid chaining critical requests

    13 chains found

    The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

    1. https://open.spotify.com/ 6kb
      1. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-dialog-container.ae962bd6.css 3kb
      2. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-context-menu-container.b615361a.css 1kb
      3. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-artist-page.8711c8e6.css 1kb
      4. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-connect-view-container.22745ba4.css 1kb
      5. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-now-playing-view.b27b04bb.css 2kb
      6. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-home.6d4808e0.css 2kb
      7. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-genre-view.3cdef6ea.css 2kb
      8. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-user-profile.05cb37ed.css 1kb
      9. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-search-results.ba0b9758.css 2kb
      10. https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-search-landing.83297305.css 1kb
      11. https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.447f22d4.css 27kb
      12. https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js 326kb
      13. https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 358kb
  5. Avoid long main-thread tasks

    4 long tasks found

    Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

    URL Start Time (ms) Duration (ms)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 8227 234
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 12790 89
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js 8469 88
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 12688 59
  6. Largest Contentful Paint element

    1 element found

    This is the largest contentful element painted within the viewport. Learn More

    Element
    li > div.Card__CardFigure-sc-1o2nsas-0 > div.Card__CardFigureImageContainer-sc-1o2nsas-1 > img.mMx2LUixlnN_Fu45JpFB
  7. Avoid large layout shifts

    1 element found

    These DOM elements contribute most to the CLS of the page.

    Element CLS Contribution
    body.mobile-web-player > div#onetrust-consent-sdk > div#onetrust-banner-sdk 0
  8. Avoid non-composited animations

    1 animated element found

    Animations which are not composited can be janky and increase CLS. Learn more

    Element Name
    body.mobile-web-player > div#onetrust-consent-sdk > div#onetrust-banner-sdk
    Failure Reason Animation
    Unsupported CSS Property: bottom slide-down-custom
  9. User Timing marks and measures

    3 user timings

    Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

    Name Type Start Time (ms) Duration (ms)
    playback_load_start Mark 8470
    snaptr Mark 14359
    snaptr Mark 15625
  10. Keep request counts low and transfer sizes small

    139 requests • 1,894 KiB

    To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

    Resource Type Requests Transfer Size (bytes)
    Total 139 1939599
    Script 31 1289367
    Font 5 406290
    Other 72 129725
    Image 16 63597
    Stylesheet 11 42934
    Document 4 7686
    Media 0 0
    Third-party 116 1921327

Passed Audits (24)

  1. Initial server response time was short

    Estimated savings 0.23 s

    Keep the server response time for the main document short because all other requests depend on it. Learn more.

    URL Time Spent (ms)
    https://open.spotify.com/ 328
  2. Avoid multiple page redirects

    Redirects introduce additional delays before the page can be loaded. Learn more.

  3. Preconnect to required origins

    Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

  4. Preload key requests

    Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn more.

  5. All text remains visible during webfont loads

    Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

  6. Minify JavaScript

    Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

  7. Minify CSS

    Minifying CSS files can reduce network payload sizes. Learn more.

  8. Minimize third-party usage

    Third-party code blocked the main thread for 0 ms

    Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

    Third-Party Transfer Size (bytes) Main-Thread Blocking Time (ms)
    Google Tag Manager 170851 0
    URL Transfer Size Blocking Time
    https://www.googletagmanager.com/gtm.js?id=GTM-PZHN3VD 94368 0
    https://www.googletagmanager.com/gtag/js?id=G-ZWG1NSHWD8&l=dataLayer&cx=c 76483 0
    Facebook 136086 0
    URL Transfer Size Blocking Time
    https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable 86927 0
    https://connect.facebook.net/en_US/fbevents.js 28194 0
    https://connect.facebook.net/signals/plugins/identity.js?v=2.9.89 20762 0
    Optanon 127136 0
    URL Transfer Size Blocking Time
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 77992 0
    https://cdn.cookielaw.org/consent/50da44be-0564-43df-b139-329aedcf267b/4113b8c4-840b-4bd0-8a77-7ff30a9f4b4d/en.json 18977 0
    https://cdn.cookielaw.org/scripttemplates/6.26.0/assets/v2/otPcCenter.json 11754 0
    https://cdn.cookielaw.org/scripttemplates/otSDKStub.js 7698 0
    Other resources 10715 0
    Fastly Insights 49739 0
    URL Transfer Size Blocking Time
    https://fastly-insights.com/api/v1/config/040e3997-282c-4275-ba9b-a406ce78b133 19240 0
    https://www.fastly-insights.com/b?k=040e3997-282c-4275-ba9b-a406ce78b133&s=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE2NzEwMzMzNjAsImV4cCI6MTY3MTAzMzQyMCwibmJmIjoxNjcxMDMzMzYwLCJzdWIiOiIwNDBlMzk5Ny0yODJjLTQyNzUtYmE5Yi1hNDA2Y2U3OGIxMzMifQ.y4546-rE11L3yJfIG52g_1hN08T7Vcfg-wliUsdqmz0 8200 0
    https://www.fastly-insights.com/insights.js?k=040e3997-282c-4275-ba9b-a406ce78b133&dnt=1 8045 0
    Other resources 14254 0
    Google Optimize 46919 0
    URL Transfer Size Blocking Time
    https://www.googleoptimize.com/optimize.js?id=GTM-W53X654 46919 0
    Pinterest 23615 0
    URL Transfer Size Blocking Time
    https://s.pinimg.com/ct/lib/main.9a94ee76.js 20997 0
    Google Analytics 20468 0
    URL Transfer Size Blocking Time
    https://www.google-analytics.com/analytics.js 20254 0
    Twitter Online Conversion Tracking 16067 0
    URL Transfer Size Blocking Time
    https://static.ads-twitter.com/uwt.js 15674 0
    Snapchat 14739 0
    URL Transfer Size Blocking Time
    https://sc-static.net/scevent.min.js 13765 0
    Scorecard Research 1183 0
    LiveRamp IdentityLink 837 0
    LinkedIn Ads 809 0
    Tapad 714 0
    Arbor 633 0
    Adobe Tag Manager 623 0
    SpeedCurve LUX 522 0
    Other Google APIs/SDKs 501 0
    Google/Doubleclick Ads 440 0
    Twitter Short URL 376 0
    Qualaroo 0 0
  9. Lazy load third-party resources with facades

    Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.

  10. JavaScript execution time

    0.7 s

    Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

    URL Total CPU Time (ms) Script Evaluation (ms) Script Parse (ms)
    Unattributable 470 48 0
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 443 396 22
    https://open.spotify.com/ 214 3 0
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js 115 90 23
    https://www.googletagmanager.com/gtm.js?id=GTM-PZHN3VD 83 77 4
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 68 50 5
  11. Minimizes main-thread work

    1.7 s

    Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

    Category Time Spent (ms)
    Script Evaluation 894
    Other 471
    Rendering 107
    Script Parsing & Compilation 84
    Style & Layout 70
    Garbage Collection 49
    Parse HTML & CSS 18
  12. Avoids an excessive DOM size

    508 elements

    A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

    Statistic Element Value
    Total DOM Elements 508
    Maximum DOM Depth button#preview-menu-button > span.IconWrapper__Wrapper-sc-16usrgb-0 > svg.Svg-sc-ytk21e-0 > path 14
    Maximum Child Elements body.mobile-web-player 13
  13. Remove duplicate modules in JavaScript bundles

    Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

  14. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.

  15. Preload Largest Contentful Paint image

    Preload the image used by the LCP element in order to improve your LCP time. Learn more.

    URL Potential Savings (ms)
    https://lite-images-i.scdn.co/image/ab67706f00000002c03728d7ade82b2a614d3e78 0
  16. Use video formats for animated content

    Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more

  17. Avoids enormous network payloads

    Total size was 1,894 KiB

    Large network payloads cost users real money and are highly correlated with long load times. Learn more.

    URL Transfer Size (bytes)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js 367054
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js 333358
    https://www.googletagmanager.com/gtm.js?id=GTM-PZHN3VD 94368
    https://encore.scdn.co/fonts/CircularSp-Bold-fe1cfc14b7498b187c78fa72fb72d148.woff2 90127
    https://encore.scdn.co/fonts/CircularSpTitle-Bold-2fbf72b606d7f0b0f771ea4956a8b4d6.woff2 87971
    https://connect.facebook.net/signals/config/1483047915331997?v=2.9.89&r=stable 86927
    https://encore.scdn.co/fonts/CircularSpTitle-Black-3f9afb402080d53345ca1850226ca724.woff2 86187
    https://encore.scdn.co/fonts/CircularSp-Book-4eaffdf96f4c6f984686e93d5d9cb325.woff2 84630
    https://cdn.cookielaw.org/scripttemplates/6.26.0/otBannerSdk.js 77992
    https://www.googletagmanager.com/gtag/js?id=G-ZWG1NSHWD8&l=dataLayer&cx=c 76483
  18. Image elements have explicit width and height

    Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more

  19. Properly size images

    Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

  20. Defer offscreen images

    Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

  21. Efficiently encode images

    Optimized images load faster and consume less cellular data. Learn more.

  22. Serve images in next-gen formats

    Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

  23. Uses passive listeners to improve scrolling performance

    Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more.

  24. Avoids document.write()

    For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn more.

Accessibility 93

Best practices (1)

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

    View Experiment!

    Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.

    Failing Elements
    head > meta Fix any of the following:
    maximum-scale on <meta> tag disables zooming on mobile devices

Additional Items to Check Manually (10)

  1. The page has a logical tab order

    Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.

  2. Interactive controls are keyboard focusable

    Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.

  3. Interactive elements indicate their purpose and state

    Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.

  4. The user's focus is directed to new content added to the page

    If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.

  5. User focus is not accidentally trapped in a region

    A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.

  6. Custom controls have associated labels

    Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.

  7. Custom controls have ARIA roles

    Custom interactive controls have appropriate ARIA roles. Learn more.

  8. Visual order on the page follows DOM order

    DOM order matches the visual order, improving navigation for assistive technology. Learn more.

  9. Offscreen content is hidden from assistive technology

    Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

  10. HTML5 landmark elements are used to improve navigation

    Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.

Passed Audits (21)

  1. [aria-*] attributes match their roles

    Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn more.

  2. [aria-hidden="true"] is not present on the document <body>

    Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn more.

  3. [aria-hidden="true"] elements do not contain focusable descendents

    Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.

  4. [role]s have all required [aria-*] attributes

    Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.

  5. [role] values are valid

    ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.

  6. [aria-*] attributes have valid values

    Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.

  7. [aria-*] attributes are valid and not misspelled

    Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.

  8. Buttons have an accessible name

    When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.

  9. The page contains a heading, skip link, or landmark region

    Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.

  10. Background and foreground colors have a sufficient contrast ratio

    Low-contrast text is difficult or impossible for many users to read. Learn more.

  11. Document has a <title> element

    The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.

  12. [id] attributes on active, focusable elements are unique

    All focusable elements must have a unique id to ensure that they're visible to assistive technologies. Learn more.

  13. ARIA IDs are unique

    The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.

  14. Heading elements appear in a sequentially-descending order

    Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.

  15. <html> element has a [lang] attribute

    If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.

  16. <html> element has a valid value for its [lang] attribute

    Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.

  17. Image elements have [alt] attributes

    Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

  18. Links have a discernible name

    Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.

  19. Lists contain only <li> elements and script supporting elements (<script> and <template>).

    Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.

  20. List items (<li>) are contained within <ul> or <ol> parent elements

    Screen readers require list items (<li>) to be contained within a parent <ul> or <ol> to be announced properly. Learn more.

  21. No element has a [tabindex] value greater than 0

    A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.

Not Applicable (22)

  1. [accesskey] values are unique

    Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.

  2. button, link, and menuitem elements have accessible names

    When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  3. ARIA input fields have accessible names

    When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  4. ARIA meter elements have accessible names

    When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  5. ARIA progressbar elements have accessible names

    When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  6. Elements with an ARIA [role] that require children to contain a specific [role] have all required children.

    Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.

  7. [role]s are contained by their required parent element

    Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.

  8. ARIA toggle fields have accessible names

    When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  9. ARIA tooltip elements have accessible names

    When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  10. ARIA treeitem elements have accessible names

    When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

  11. <dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

    When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.

  12. Definition list items are wrapped in <dl> elements

    Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn more.

  13. No form fields have multiple labels

    Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.

  14. <frame> or <iframe> elements have a title

    Screen reader users rely on frame titles to describe the contents of frames. Learn more.

  15. <input type="image"> elements have [alt] text

    When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.

  16. Form elements have associated labels

    Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

  17. The document does not use <meta http-equiv="refresh">

    Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.

  18. <object> elements have alternate text

    Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more.

  19. Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.

    Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.

  20. <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.

    Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.

  21. [lang] attributes have a valid value

    Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.

  22. <video> elements contain a <track> element with [kind="captions"]

    When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.

Best Practices 83

Trust and Safety (1)

  1. Ensure CSP is effective against XSS attacks

    A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more

    Description Directive Severity
    Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can. object-src High
    Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary. script-src High
    Consider adding 'unsafe-inline' (ignored by browsers supporting nonces/hashes) to be backward compatible with older browsers. script-src Medium

General (4)

  1. Detected JavaScript libraries

    All front-end JavaScript libraries detected on the page. Learn more.

    Name Version
    React
    core-js core-js-global@3.26.1; core-js-pure@3.0.0
  2. Browser errors were logged to the console

    Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

    Source Description
    • URL: https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js
    • Line: 0
    • Column: 41116
    Error sending hit payload length to Google Analytics
    • URL: https://www.googletagmanager.com/gtm.js?id=GTM-PZHN3VD
    • Line: 53
    • Column: 463
    Refused to load the script 'https://cl.qualaroo.com/ki.js/51746/b0R.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' blob: open.spotifycdn.com open-review.spotifycdn.com quicksilver.scdn.co www.google-analytics.com www.googletagmanager.com static.ads-twitter.com analytics.twitter.com s.pinimg.com sc-static.net https://www.google.com/recaptcha/ cdn.ravenjs.com connect.facebook.net www.gstatic.com sb.scorecardresearch.com pixel-static.spotify.com optimize.google.com cdn.cookielaw.org geolocation.onetrust.com www.googleoptimize.com www.fastly-insights.com static.hotjar.com script.hotjar.com https://www.googleadservices.com/pagead/conversion_async.js https://www.googleadservices.com/pagead/conversion/ https://analytics.tiktok.com/i18n/pixel/sdk.js https://analytics.tiktok.com/i18n/pixel/identify.js https://analytics.tiktok.com/i18n/pixel/config.js https://www.redditstatic.com/ads/pixel.js cdn.speedcurve.com 'sha256-WfsTi7oVogdF9vq5d14s2birjvCglqWF842fyHhzoNw=' 'sha256-KRzjHxCdT8icNaDOqPBdY0AlKiIh5F8r4bnbe1PQwss=' 'sha256-Z5wh7XXSBR1+mTxLSPFhywCZJt77+uP1GikAgPIsu2s='". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
    • URL: https://sc-static.net/scevent.min.js
    • Line: 0
    • Column: 24474
    Refused to load the script 'https://tr.snapchat.com/config/com/fff7f198-e6aa-4833-b900-92d3854473b2.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' blob: open.spotifycdn.com open-review.spotifycdn.com quicksilver.scdn.co www.google-analytics.com www.googletagmanager.com static.ads-twitter.com analytics.twitter.com s.pinimg.com sc-static.net https://www.google.com/recaptcha/ cdn.ravenjs.com connect.facebook.net www.gstatic.com sb.scorecardresearch.com pixel-static.spotify.com optimize.google.com cdn.cookielaw.org geolocation.onetrust.com www.googleoptimize.com www.fastly-insights.com static.hotjar.com script.hotjar.com https://www.googleadservices.com/pagead/conversion_async.js https://www.googleadservices.com/pagead/conversion/ https://analytics.tiktok.com/i18n/pixel/sdk.js https://analytics.tiktok.com/i18n/pixel/identify.js https://analytics.tiktok.com/i18n/pixel/config.js https://www.redditstatic.com/ads/pixel.js cdn.speedcurve.com 'sha256-WfsTi7oVogdF9vq5d14s2birjvCglqWF842fyHhzoNw=' 'sha256-KRzjHxCdT8icNaDOqPBdY0AlKiIh5F8r4bnbe1PQwss=' 'sha256-Z5wh7XXSBR1+mTxLSPFhywCZJt77+uP1GikAgPIsu2s='". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
  3. Missing source maps for large first-party JavaScript

    Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.

    URL Map URL
    https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js https://open.spotifycdn.com/cdn/build/mobile-web-player/vendor~mobile-web-player.ab2b0eb5.js.map
    Error
    Large JavaScript file is missing a source map
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js https://open.spotifycdn.com/cdn/build/mobile-web-player/mobile-web-player.6a62f7b6.js.map
    Error
    Large JavaScript file is missing a source map
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-now-playing-view.b27b04bb.js https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-now-playing-view.b27b04bb.js.map
    Error
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-home.6d4808e0.js https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-home.6d4808e0.js.map
    Error
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-dialog-container.ae962bd6.js https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-dialog-container.ae962bd6.js.map
    Error
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-context-menu-container.b615361a.js https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-context-menu-container.b615361a.js.map
    Error
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-connect-view-container.22745ba4.js https://open.spotifycdn.com/cdn/build/mobile-web-player/mwp-connect-view-container.22745ba4.js.map
    Error
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/94.291eaf4d.js https://open.spotifycdn.com/cdn/build/mobile-web-player/94.291eaf4d.js.map
    Error
    Error: Failed fetching source map (404)
    https://open.spotifycdn.com/cdn/build/mobile-web-player/692.22cf626c.js https://open.spotifycdn.com/cdn/build/mobile-web-player/692.22cf626c.js.map
    Error
    Error: Failed fetching source map (404)
  4. Issues were logged in the Issues panel in Chrome Devtools

    Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

    Issue type
    Content security policy
    URL
    https://cl.qualaroo.com/ki.js/51746/b0R.js
    https://tr.snapchat.com/config/com/fff7f198-e6aa-4833-b900-92d3854473b2.js

Passed Audits (10)

  1. Uses HTTPS

    All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.

  2. Avoids requesting the geolocation permission on page load

    Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.

  3. Avoids requesting the notification permission on page load

    Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.

  4. Avoids front-end JavaScript libraries with known security vulnerabilities

    Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.

  5. Allows users to paste into password fields

    Preventing password pasting undermines good security policy. Learn more.

  6. Displays images with correct aspect ratio

    Image display dimensions should match natural aspect ratio. Learn more.

  7. Serves images with appropriate resolution

    Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.

  8. Page has the HTML doctype

    Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.

  9. Properly defines charset

    A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.

  10. Avoids deprecated APIs

    Deprecated APIs will eventually be removed from the browser. Learn more.

Not Applicable (1)

  1. Fonts with font-display: optional are preloaded

    Preload optional fonts so first-time visitors may use them. Learn more

SEO 100

Additional Items to Check Manually (1)

  1. Structured data is valid

    Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.

Passed Audits (12)

  1. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.

  2. Document has a <title> element

    The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.

  3. Document has a meta description

    Meta descriptions may be included in search results to concisely summarize page content. Learn more.

  4. Page has successful HTTP status code

    Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.

  5. Links have descriptive text

    Descriptive link text helps search engines understand your content. Learn more.

  6. Links are crawlable

    Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More

  7. Page isn’t blocked from indexing

    Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.

  8. robots.txt is valid

    If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.

  9. Image elements have [alt] attributes

    Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

  10. Document has a valid hreflang

    hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.

  11. Document has a valid rel=canonical

    Canonical links suggest which URL to show in search results. Learn more.

  12. Document avoids plugins

    Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.

Not Applicable (2)

  1. Document uses legible font sizes

    Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.

  2. Tap targets are sized appropriately

    Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

PWA 56

Installable (1)

  1. Web app manifest and service worker meet the installability requirements

    Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.

PWA Optimized (7)

  1. Does not register a service worker that controls page and start_url

    The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.

  2. Configured for a custom splash screen

    A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.

  3. Does not set a theme color for the address bar.

    The browser address bar can be themed to match your site. Learn more.

    Failures:
    • No <meta name="theme-color"> tag found

  4. Content is sized correctly for the viewport

    If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.

  5. Has a <meta name="viewport"> tag with width or initial-scale

    A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.

  6. Does not provide a valid apple-touch-icon

    For ideal appearance on iOS when users add a progressive web app to the home screen, define an apple-touch-icon. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

  7. Manifest doesn't have a maskable icon

    A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.

Additional Items to Check Manually (3)

  1. Site works cross-browser

    To reach the most number of users, sites should work across every major browser. Learn more.

  2. Page transitions don't feel like they block on the network

    Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.

  3. Each page has a URL

    Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.