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 more
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 more.
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)
233.625x105
1000x450
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (2)
Show Hide
Avoids an excessive DOM size 155 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
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
155.0
Maximum DOM Depth
Oscar:
<span class="text-gray-400 mr-2">
11.0
Maximum Child Elements
body
<body>
17.0
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.
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected 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.
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">
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 more.
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 …
<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 …
<div class="flex flex-row flex-wrap sm:flex-nowrap p-2 mb-4 hover:bg-gray-100 cursor-p…">
These are opportunities to improve the legibility of your content.
Additional items to manually check (10)
Show Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
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.
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.
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.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
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.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (18)
Show Hide
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[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.
[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.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
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.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
[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.
[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.
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.
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.
<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.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
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.
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.
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.
Not applicable (24)
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.
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.
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.
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.
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.
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.
[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.
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.
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.
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.
<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.
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.
[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.
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.
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.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<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.
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.
<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.
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.
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.
<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.
[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.
<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.
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Library Version
Vulnerability Count
Highest Severity
3
Medium
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 more.
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/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
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
React
Next.js
10.0.6
Passed audits (3)
Show Hide
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
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.
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.
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">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Mobile Friendly
Tap targets are not sized appropriately 75% appropriately sized tap targets
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.
Tap Target
Size
Overlapping Target
Terms of Service
<a href="/terms">
65x11
Privacy Policy
<a href="/privacy">
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (7)
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.
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.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
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
Document uses legible font sizes 74.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.
Source
Selector
% of Page Text
Font Size
…css/08dcb44….css:1:14054
(www.mikescerealshack.co)
.text-2xs
25.43%
8px
Legible text
74.57%
≥ 12px
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
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.