https://www.mikescerealshack.co/search?q=call+of+duty
Diagnostics
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Next.jsUse the next/image component to make sure images are always sized appropriately. Learn more.
URL
Mike's Cereal Shack Co Logo - The Office Meme Creator
<img src="/logo-text.svg" class="h-10" alt="Mike's Cereal Shack Co Logo - The Office Meme Creator">
/logo-text.svg
(www.mikescerealshack.co)
Images were larger than their displayed size
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
URL
Displayed dimensions
Actual dimensions
Mike's Cereal Shack Co Logo - The Office Meme Creator
<img src="/logo-text.svg" class="h-10" alt="Mike's Cereal Shack Co Logo - The Office Meme Creator">
/logo-text.svg
(www.mikescerealshack.co)
178x80
1000x450
Avoids an excessive DOM size 361 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
ReactConsider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.
Statistic
Element
Value
Total DOM Elements
361
Maximum DOM Depth
Oscar:
<span class="text-gray-400 mr-2">
11
Maximum Child Elements
body
<body>
17
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (1)
Show Hide
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 about using the viewport meta tag.
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.
Names and labels
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/81d89db1bf3d43b5b21f813…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/7026b6c1508a8c97799215a…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s3/e3/128w/9b3031eb3988ba363fe94692…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s3/e3/128w/5de94bb353874938309d3f80…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s3/e3/128w/793a408ca63a660b5d7aa1a4…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s3/e3/128w/a8a4fc239c89991d59a855ce…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s7/e11/128w/5d1df07b1741f4c3e66ed20…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s7/e11/128w/db42e8a6a975219d129746b…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/b997cdb40263ff124e2a245…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/0ee3717ac7e98ad517cd3cb…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e3/128w/08b3049589ca7ae688b0f771…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e3/128w/de01862a7d12870103fde1e6…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/f5c5012a2afa2ac6b190dcd…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/00e4016f570fc5ecc507aaa…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s9/e9/128w/5fbc916d0fffb01af1225d4e…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s9/e9/128w/cd9888a027f56d35db822422…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s9/e9/128w/558dc2f7d9c947e5445fb3f1…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s9/e9/128w/2327f35f501cfa8a6f6a47c8…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Oscar:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Angela:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Kevin:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Karen:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
3:34-4:07
<div class="text-gray-500 text-xs leading-normal">
S3E3 The Coup 3:34-4:07 Jim:… game called Call of Duty, and t…
<div class="flex flex-row flex-wrap sm:flex-nowrap p-2 mb-4 hover:bg-gray-100 cursor-p…">
Jim:
<span class="text-gray-400 mr-2">
S3E3 The Coup 3:34-4:07 Jim:… game called Call of Duty, and t…
<div class="flex flex-row flex-wrap sm:flex-nowrap p-2 mb-4 hover:bg-gray-100 cursor-p…">
Dwight:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Toby:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Andy:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Ernesto:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Nate:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Dwight:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Erin:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Andy:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Oscar:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Dwight:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Darryl:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Andy:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Pam:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Dwight:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Oscar:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Phyllis:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Meredith:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
Dwight:
<span class="text-gray-400 mr-2">
"call of duty" Search Results Go S8E13 Jury Duty 10:41-11:34 Oscar:Wow, it's so…
<main id="main-content" class="w-full bg-white rounded-lg p-4 relative overflow-hidden" style="box-shadow: black 0px 2px 1px;">
These are opportunities to improve the legibility of your content.
Best practices
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Failing Elements
Terms of Service
<a href="/terms">
Privacy Policy
<a href="/privacy">
Privacy Policy
<a href="/privacy">
Terms of Service
<a href="/terms">
These items highlight common accessibility best practices.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
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 how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
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 how to avoid focus traps.
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 how to direct focus to new content.
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. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (22)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[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 how aria-hidden affects the document body.
[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 about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
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 how to make buttons more accessible.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
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 about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[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 how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
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 about document titles.
<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 about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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 about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
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 about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (32)
Show Hide
[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 about access keys.
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 how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
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 about input field labels.
ARIA meter elements have accessible names
When a meter 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 how to name meter elements.
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 how to label progressbar elements.
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 about roles and required children elements.
[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 about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
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 about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip 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 how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem 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 about labeling treeitem elements.
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 about bypass blocks.
<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 how to structure definition lists correctly.
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 how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
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 how to use form labels.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<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 about input image alt text.
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 about the refresh meta tag.
<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 about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
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 about the tabindex attribute.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
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 about the headers attribute.
<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 about table headers.
[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 how to use the lang attribute.
<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 about video captions.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
URL
Displayed size
Actual size
Expected size
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s3/e3/128w/793a408ca63a660b5d7aa1a4…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s3/e3/128w/a8a4fc239c89991d59a855ce…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
…128w/793a408….jpg
(cdn.mikescerealshack.co)
112 x 64
128 x 72
224 x 128
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s3/e3/128w/9b3031eb3988ba363fe94692…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s3/e3/128w/5de94bb353874938309d3f80…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
…128w/9b3031e….jpg
(cdn.mikescerealshack.co)
112 x 64
128 x 72
224 x 128
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s7/e11/128w/5d1df07b1741f4c3e66ed20…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s7/e11/128w/db42e8a6a975219d129746b…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
…128w/5d1df07….jpg
(cdn.mikescerealshack.co)
112 x 64
128 x 72
224 x 128
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/81d89db1bf3d43b5b21f813…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/7026b6c1508a8c97799215a…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
…128w/81d89db….jpg
(cdn.mikescerealshack.co)
112 x 64
128 x 72
224 x 128
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/b997cdb40263ff124e2a245…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/0ee3717ac7e98ad517cd3cb…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
…128w/b997cdb….jpg
(cdn.mikescerealshack.co)
112 x 64
128 x 72
224 x 128
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Name
Version
React
Next.js
10.0.6
Passed audits (5)
Show Hide
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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 about using the viewport meta tag.
Document uses legible font sizes 88.57% legible text
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 about legible font sizes.
Source
Selector
% of Page Text
Font Size
…css/08dcb44….css:1:14054
(www.mikescerealshack.co)
.text-2xs
11.43%
8px
Legible text
88.57%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
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
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Failing Elements
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/81d89db1bf3d43b5b21f813…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/7026b6c1508a8c97799215a…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s3/e3/128w/9b3031eb3988ba363fe94692…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s3/e3/128w/5de94bb353874938309d3f80…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s3/e3/128w/793a408ca63a660b5d7aa1a4…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s3/e3/128w/a8a4fc239c89991d59a855ce…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s7/e11/128w/5d1df07b1741f4c3e66ed20…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s7/e11/128w/db42e8a6a975219d129746b…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/b997cdb40263ff124e2a245…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/0ee3717ac7e98ad517cd3cb…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e3/128w/08b3049589ca7ae688b0f771…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e3/128w/de01862a7d12870103fde1e6…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s8/e13/128w/f5c5012a2afa2ac6b190dcd…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s8/e13/128w/00e4016f570fc5ecc507aaa…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s9/e9/128w/5fbc916d0fffb01af1225d4e…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s9/e9/128w/cd9888a027f56d35db822422…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
a > div.flex > div > img.h-16
<img src="https://cdn.mikescerealshack.co/frames/s9/e9/128w/558dc2f7d9c947e5445fb3f1…" fallbacksrc="https://cdn.mikescerealshack.co/frames/s9/e9/128w/2327f35f501cfa8a6f6a47c8…" class="h-16 w-28 sm:h-24 sm:w-44 max-w-none">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run these additional validators on your site to check additional SEO best practices.
Passed audits (4)
Show Hide
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 about document titles.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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 how to make links crawlable
Not applicable (1)
Show Hide
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 about robots.txt.