C — https://www.midjourney.com

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

Page weighs 18.7 MB (14.7 MB transferred)

Performance › Page Weight Budget

Soft 404: server returns HTTP 200 for non-existent pages

Accessibility › 404 Error Page

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.midjourney.com)](https://beavercheck.com/results/66f99121-38e9-2d1c-d3db-44927261df26)

HTML

<a href="https://beavercheck.com/results/66f99121-38e9-2d1c-d3db-44927261df26"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.midjourney.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.midjourney.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

10.68 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

38.66 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

120.30 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

23.31 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

201.73 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

Request	Cache TTL	Transfer Size
www.midjourney.com/public/assets/images/homepage/eye.png	14400.0 s	2.5 MiB
www.midjourney.com/public/assets/images/homepage/people.png	14400.0 s	2.2 MiB
www.midjourney.com/public/assets/images/homepage/brain.png	14400.0 s	1.8 MiB
www.midjourney.com/public/assets/images/homepage/face.png	14400.0 s	1.6 MiB
www.midjourney.com/public/assets/images/homepage/heart.png	14400.0 s	1.4 MiB
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	14400.0 s	1.2 MiB
www.midjourney.com/public/assets/images/homepage/lips.png	14400.0 s	1.2 MiB
www.midjourney.com/public/assets/images/homepage/pen.png	14400.0 s	1.1 MiB
www.midjourney.com/public/assets/images/homepage/hand.png	14400.0 s	1.0 MiB
www.midjourney.com/__/auth/iframe.js	14400.0 s	90.2 KiB
www.midjourney.com/public/out/clientSideEntry-pskma55q.css	14400.0 s	44.1 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/...	14400.0 s	11.5 KiB
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....	2819.0 s	726 B

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
/css2?family=DM+Sans:opsz,wght@9..40,400..700&family=JetB...	1.2 KiB	813 ms
challenges.cloudflare.com/turnstile/v0/b/625261456364/api.js	17.3 KiB	764 ms
www.midjourney.com/public/out/clientSideEntry-pskma55q.css	44.1 KiB	1.6 s
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....	726 B	496 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
Eye `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/eye.png	2.5 MiB	2.4 MiB
People `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/people.png	2.2 MiB	2.2 MiB
Brain `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/brain.png	1.8 MiB	1.8 MiB
Face `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/face.png	1.6 MiB	1.5 MiB
Heart `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/heart.png	1.4 MiB	1.4 MiB
Lips `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/lips.png	1.2 MiB	1.2 MiB
Pen `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/pen.png	1.1 MiB	1.1 MiB
Hand `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/hand.png	1.0 MiB	1.0 MiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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

Estimated savings: 4.4 s 971.4 KiB

URL	Transfer Size	Est Savings
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	1.2 MiB	866.6 KiB
www.midjourney.com/__/auth/iframe.js	89.8 KiB	54.9 KiB
www.googletagmanager.com/gtag/js?id=AW-16508112792	145.9 KiB	49.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	170.2 s	31.9 s	23 ms
Unattributable	2.6 s	154 ms	0.0 ms
www.midjourney.com/	973 ms	46 ms	2.4 ms
www.midjourney.com/__/auth/iframe.js	606 ms	547 ms	37 ms
www.googletagmanager.com/gtag/js?id=AW-16508112792	522 ms	409 ms	58 ms
www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	349 ms	277 ms	3.0 ms
/_/scs/abc-static/_/js/k=gapi.lb.en.PJsh2cctCQI.O/m=gapi_...	118 ms	100 ms	14 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Other	140.3 s
Script Evaluation	33.6 s
Rendering	744 ms
Style & Layout	532 ms
Garbage Collection	220 ms
Script Parsing & Compilation	149 ms
Parse HTML & CSS	44 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.midjourney.com/public/assets/images/homepage/eye.png	2.5 MiB
www.midjourney.com/public/assets/images/homepage/people.png	2.2 MiB
www.midjourney.com/public/assets/images/homepage/brain.png	1.8 MiB
www.midjourney.com/public/assets/images/homepage/face.png	1.6 MiB
www.midjourney.com/public/assets/images/homepage/heart.png	1.4 MiB
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	1.2 MiB
www.midjourney.com/public/assets/images/homepage/lips.png	1.2 MiB
www.midjourney.com/public/assets/images/homepage/pen.png	1.1 MiB
www.midjourney.com/public/assets/images/homepage/hand.png	1.0 MiB
www.googletagmanager.com/gtag/js?id=AW-16508112792	146.3 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 250 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 180 ms

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

○Avoid large layout shifts

100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●`button`, `link`, and `menuitem` elements have accessible names

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○ARIA attributes are used as specified for the element's role

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○The page contains a heading, skip link, or landmark region

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

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Deprecation / Warning	Source
SharedStorage	www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
AttributionReporting	www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js line 100, col 474

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 about source maps.

URL
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.72 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.72 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

14.01 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.38 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

48.08 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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

Request	Cache TTL	Transfer Size
www.midjourney.com/public/assets/images/homepage/eye.png	14400.0 s	2.5 MiB
www.midjourney.com/public/assets/images/homepage/people.png	14400.0 s	2.2 MiB
www.midjourney.com/public/assets/images/homepage/brain.png	14400.0 s	1.8 MiB
www.midjourney.com/public/assets/images/homepage/face.png	14400.0 s	1.6 MiB
www.midjourney.com/public/assets/images/homepage/heart.png	14400.0 s	1.4 MiB
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	14400.0 s	1.2 MiB
www.midjourney.com/public/assets/images/homepage/lips.png	14400.0 s	1.2 MiB
www.midjourney.com/public/assets/images/homepage/pen.png	14400.0 s	1.1 MiB
www.midjourney.com/public/assets/images/homepage/hand.png	14400.0 s	1.0 MiB
www.midjourney.com/public/out/clientSideEntry-pskma55q.css	14400.0 s	44.1 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/625261456364/...	14400.0 s	13.4 KiB
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....	2819.0 s	726 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:46.483 source:map[type:text value:[unattributed]]]]

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

URL	Transfer Size	Duration
/css2?family=DM+Sans:opsz,wght@9..40,400..700&family=JetB...	1.2 KiB	266 ms
www.midjourney.com/public/out/clientSideEntry-pskma55q.css	44.1 KiB	212 ms
challenges.cloudflare.com/turnstile/v0/b/625261456364/api.js	17.4 KiB	215 ms
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....	726 B	166 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
Eye `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/eye.png	2.5 MiB	2.4 MiB
People `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/people.png	2.2 MiB	2.2 MiB
Brain `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/brain.png	1.8 MiB	1.8 MiB
Face `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/face.png	1.6 MiB	1.6 MiB
Heart `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/heart.png	1.4 MiB	1.4 MiB
Lips `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/lips.png	1.2 MiB	1.2 MiB
Pen `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/pen.png	1.1 MiB	1.1 MiB
Hand `div.my-6 > div.grid > div.relative > img.w-full`	www.midjourney.com/public/assets/images/homepage/hand.png	1.0 MiB	1.0 MiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Diagnostics

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

Estimated savings: 680 ms 917.5 KiB

URL	Transfer Size	Est Savings
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	1.2 MiB	867.6 KiB
www.googletagmanager.com/gtag/js?id=AW-16508112792	145.9 KiB	49.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

URL	Total CPU Time	Script Evaluation	Script Parse
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	43.3 s	9.2 s	5.5 ms
Unattributable	739 ms	39 ms	0.0 ms
www.midjourney.com/	248 ms	34 ms	0.8 ms
www.googletagmanager.com/gtag/js?id=AW-16508112792	101 ms	86 ms	14 ms
www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	80 ms	77 ms	1.0 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Category	Time Spent
Other	34.7 s
Script Evaluation	9.5 s
Rendering	147 ms
Style & Layout	132 ms
Garbage Collection	83 ms
Script Parsing & Compilation	24 ms
Parse HTML & CSS	10 ms

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

URL	Transfer Size
www.midjourney.com/public/assets/images/homepage/eye.png	2.5 MiB
www.midjourney.com/public/assets/images/homepage/people.png	2.2 MiB
www.midjourney.com/public/assets/images/homepage/brain.png	1.8 MiB
www.midjourney.com/public/assets/images/homepage/face.png	1.6 MiB
www.midjourney.com/public/assets/images/homepage/heart.png	1.4 MiB
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js	1.2 MiB
www.midjourney.com/public/assets/images/homepage/lips.png	1.2 MiB
www.midjourney.com/public/assets/images/homepage/pen.png	1.1 MiB
www.midjourney.com/public/assets/images/homepage/hand.png	1.0 MiB
www.googletagmanager.com/gtag/js?id=AW-16508112792	146.3 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 20 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 60 ms

●Server Backend Latencies 290 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 170 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

100

Accessibility

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●`button`, `link`, and `menuitem` elements have accessible names

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○ARIA attributes are used as specified for the element's role

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○The page contains a heading, skip link, or landmark region

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

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

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

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

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

Deprecation / Warning	Source
SharedStorage	www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.midjourney.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
AttributionReporting	www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js line 100, col 474

URL
www.midjourney.com/public/out/clientSideEntry-fawaqcm4.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

SEO

Content Best Practices

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

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.midjourney.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts