Fix common website issues, step by step
Each guide explains why an issue matters and how to fix it on your platform. Run a free audit to see which ones apply to your site.
Performance
- How to fix “Image elements do not have explicit width and height”
Images without a width and height make your page jump as they load, which annoys visitors and hurts your Core Web Vitals. How to fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Improve image delivery”: smaller, faster images
Images are the heaviest part of most web pages. How to resize, compress and serve them in modern formats on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js, without losing quality.
- How to fix render-blocking requests (CSS and JavaScript)
Scripts and stylesheets that load before anything appears keep your page blank. How to defer what can wait, on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to reduce unused JavaScript
Most sites load scripts they never use: old apps, plugins and tracking tags. Every one slows taps and clicks. How to find and remove them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix a slow Largest Contentful Paint (LCP)
LCP is when the biggest thing at the top of your page appears, usually the main image. How to make it load first on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix a slow First Contentful Paint (FCP) and Speed Index
How long visitors stare at a blank screen. The usual causes (slow server, blocking files, web fonts) and how to fix them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to reduce Total Blocking Time (and JavaScript execution time)
When scripts keep the browser busy, taps and clicks wait. How to find the heavy scripts and cut them down on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix a slow server response, redirects and missing compression
Everything waits for the first response from your server. How to cut redirects, speed up the server and turn on compression on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix long critical request chains (network dependency tree)
When one file has to load before the browser even finds the next, every step adds a round trip. How to shorten those chains on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Font display”: keep text visible while fonts load
Text that stays invisible until a web font downloads. How to set font-display: swap on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Use efficient cache lifetimes”
Files the browser has to download again on every visit. How to set long cache lifetimes with Cache-Control, and what you can and can't change on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Legacy JavaScript”: stop shipping code for old browsers
Polyfills and transforms for browsers almost nobody uses any more. What they cost, who can fix them, and how to change your build on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Optimize DOM size”: pages with too many elements
Very large pages make every style change and layout slow, so taps feel sluggish. How to trim them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix layout shifts (Cumulative Layout Shift, CLS)
Content that jumps as the page loads, so visitors tap the wrong thing. How to find what moves and stop it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to reduce unused CSS, minify CSS and JavaScript, and remove duplicate code
Stylesheets full of rules the page never uses, files that still contain comments and spaces, and the same library shipped twice. How to trim them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix forced reflow (layout thrashing)
Scripts that change the page and then immediately measure it, forcing the browser to redo its layout again and again. How to find the code and batch reads and writes.
- How to fix “Avoid enormous network payloads” (page weight)
Pages that download several megabytes before they're done. Where the weight usually comes from and how to cut it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Page prevented back/forward cache restoration”
When visitors press Back, browsers can show the previous page instantly from memory, unless something on it opts out. The usual blockers and how to remove them.
Accessibility
- How to fix low color contrast on your website
Text that's too light against its background is hard to read for many visitors, and fails WCAG. What the 4.5:1 rule means and how to fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to add alt text to images (and when to leave it empty)
Images without alt text are silent or confusing for screen reader users and invisible to search engines. How to write good alt text and add it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Links do not have a discernible name” (icon links)
Icon-only links (social icons, a cart, a logo image) are announced as just "link" to screen reader users. How to give them a name on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix the viewport meta tag (zoom disabled or not optimized for mobile)
One line in your page's <head> controls how phones size the page and whether visitors can zoom. How to fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Form elements do not have associated labels”
Form fields that rely on placeholder text alone are unnamed for screen reader users. How to label newsletter, search and contact fields on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Buttons do not have an accessible name” (icon buttons)
Icon-only buttons such as menu, close, search, cart and slider arrows are announced as just "button". How to name them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix heading order (skipped heading levels and empty headings)
Headings that jump from H1 to H4, or exist only for styling, break the page outline screen reader users navigate by. How to fix them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to set your page's language (the lang attribute)
Without a language on the page, screen readers may read your text with the wrong accent and pronunciation. How to set it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix small tap targets (“Touch targets do not have sufficient size or spacing”)
Links and buttons too small or too close together to tap reliably. How to give them room on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Frames do not have a title” (embedded maps, videos and widgets)
Embedded maps, videos, booking widgets and forms load in frames that screen readers announce only as "frame". How to give them a title on any platform.
- How to add captions to videos (“<video> elements do not contain a captions track”)
Videos without captions shut out deaf and hard-of-hearing visitors, and anyone watching with the sound off. How to add them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “aria-hidden elements contain focusable descendants”
Hidden menus, slides and pop-ups that keyboard users can still tab into, but screen readers won't announce. How to hide them properly.
- How to fix ARIA dialogs, fields and toggles without an accessible name
Custom pop-ups, dropdowns, switches and progress bars built with ARIA roles that screen readers can't name. How to label them.
- How to fix invalid ARIA (roles, attributes and duplicate IDs)
Misspelled ARIA attributes, roles used on the wrong elements, and labels pointing at duplicate IDs make screen readers report the page incorrectly. How to find and fix them.
- How to fix list markup (lists must only contain list items)
Lists with stray elements inside, list items without a list, and ARIA roles missing their parent or children. Why screen readers care and how to fix the markup.
- How to fix “Some elements have a tabindex value greater than 0”
Positive tabindex values force a custom tab order that skips around the page and confuses keyboard users. How to remove them, and why duplicate accesskeys cause similar trouble.
- How to add a skip link and a main landmark
Keyboard and screen reader users have to wade through your whole header on every page unless they can jump straight to the content. How to add a working skip link and <main> region.
- How to fix data table headers (size charts, price and spec tables)
Tables whose header cells aren't connected to their data leave screen reader users hearing numbers without context. How to mark up size charts and comparison tables correctly.
- How to fix “The document uses <meta http-equiv="refresh">”
Pages that reload or redirect themselves after a delay pull visitors away mid-read. How to replace a meta refresh with a proper redirect.
- How to fix “Links rely on color to be distinguishable”
Links inside paragraphs that look different only by color are invisible to many colorblind visitors. The simple fix is an underline.
SEO
- How to add a meta description that gets clicks
Your meta description is your pitch in search results. Without one, search engines pick text from the page for you. How to write one and add it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Links do not have descriptive text”
Links that say "click here" or "read more" tell search engines and screen reader users nothing about where they lead. How to rewrite them, including fixed theme buttons, on any platform.
- How to fix “Document doesn't have a <title> element”
The page title is the first thing screen readers announce and the headline of your search result. How to set it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Page is blocked from indexing” (noindex)
A noindex tag or header tells search engines to leave a page out of their results. How to find where it comes from and remove it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Page has unsuccessful HTTP status code” (404 and 500 errors)
The page you audited answered with an error code, so search engines may drop it. How to find out why and fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Links are not crawlable”
Links built with JavaScript click handlers instead of a real address are invisible to search engines, so the pages they lead to may never be found. How to fix them.
- How to fix “robots.txt is not valid”
The robots.txt file tells search engines which parts of your site to crawl. A broken one can block your whole site or confuse crawlers. How to fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Document doesn't have a valid hreflang”
hreflang tags tell search engines which language or country each version of a page is for. Invalid codes mean the wrong version shows in search results. How to fix them.
- How to fix “Document doesn't have a valid rel=canonical”
The canonical tag tells search engines which address is the main version of a page. A wrong one can send your ranking to another page, or another site. How to fix it.
Security
- How to add the Strict-Transport-Security (HSTS) header
Make browsers always load your site over HTTPS, so visitors on public Wi-Fi can't be sent to an insecure copy. Steps for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to add a Content-Security-Policy (CSP) header without breaking your site
A Content-Security-Policy limits what a hacked or tampered page can do. Start with a safe policy that won't break anything, then tighten it. Steps for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to add the X-Content-Type-Options: nosniff header
One line that stops browsers guessing file types, which closes off a class of attacks using uploaded files. Steps for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to stop other sites embedding your pages (clickjacking protection)
Without frame protection, any site can load your pages invisibly inside its own and trick visitors into clicking. One header fixes it. Steps for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to add a Referrer-Policy header
Control how much of your page addresses other sites can see when visitors follow links. Low risk on modern browsers, but quick to set. Steps for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix “Site isn't served over HTTPS”
Without HTTPS, browsers label your site "Not secure" and anything visitors send can be read or changed on the way. How to turn it on for Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix an expiring or expired SSL certificate
When your certificate expires, browsers show a full-page warning and most visitors leave. How to renew it, and make sure it renews automatically, on any platform.
UX & conversion
- How to fix “Browser errors were logged to the console”
JavaScript errors and failed requests that the browser reports while your page loads. How to find what's broken and who can fix it.
- How to fix “Uses deprecated APIs”
Code that relies on browser features scheduled for removal. It works today and breaks later. How to find it and who needs to update it.
- How to fix “Uses third-party cookies”
Embedded services that set cookies from their own domain may stop working when browsers or visitors block them. How to find which ones, and what to do about each.
- How to fix location and notification requests on page load
Pages that ask for a visitor's location, or permission to send notifications, the moment they open. Why it backfires and how to ask at the right time.
- How to fix “Prevents users from pasting into input fields”
Blocking paste in password, email or confirmation fields makes them harder to use and pushes people toward weaker passwords. How to remove it.
- How to fix distorted or blurry images (aspect ratio and resolution)
Images squashed out of shape, or too low-resolution for the screen they're shown on. How to fix the CSS and serve the right size on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- How to fix a missing doctype or character encoding
Two lines at the very top of every page tell browsers how to render it and how to read its characters. Without them, layouts break and text can turn into gibberish.