fawry.com

Of everything your server sends for this page, very little is actual readable text. The rest is code, styling, and markup wrapper. Agents fetched a lot of bytes and found few words.

Agents work with retrieval budgets. A page that is 2% text either gets skimmed (and mis-summarised) or skipped. More signal per byte means more of your actual message survives into the agent’s summary.

1. Confirm your real copy is server-rendered. See the JavaScript check; these two usually fail together.
2. Cut boilerplate wrappers: deeply nested divs, inline SVG logos repeated per section, base64 images inlined into HTML.
3. Move large inline styles and scripts into external files.
4. Check how much of the document is inline script: your report now says. If most of it is, that is your framework serializing state for hydration, often a second copy of text already in the HTML. Send only the props a component cannot recompute, and render statically where a page does not need to hydrate.

• Re-scan: "Text-to-markup ratio" improves, and "Page weight" often improves alongside.

• Don’t pad the page with keyword text to inflate the ratio. The ratio is a proxy for substance, and stuffing is the opposite of substance.

Headings (H1, H2, H3…) are the page’s outline. Yours skip levels, repeat H1s, or use styled text instead of real heading tags, so the outline machines extract is scrambled.

Agents use the heading tree to navigate long pages and to decide which section answers a question. A broken tree means quotes get attributed to the wrong section, or sections are missed entirely.

1. Exactly one H1 per page: the page’s actual title.
2. Nest without skipping: H2 for sections, H3 for subsections. Never jump H1 to H4 for visual size.
3. If a heading looks right but is a styled <div>, make it a real <h2> and adjust CSS. Machines only see tags.

• Re-scan: "Heading hierarchy" flips to PASS.

• Don’t pick heading levels for their font size; style with CSS and keep levels semantic.

The <title> tag is the page’s name: the text in the browser tab. Yours is missing, empty, or generic (e.g. just "Home"), so machines have no usable name for this page.

The title is the single most-quoted identifier for a page; agents cite it verbatim when referencing you. A missing one gets replaced with a guess assembled from headings, which amounts to your page’s name being written by someone else.

1. Give every page a unique, descriptive title in the shape "What the page is | Brand", under about 60 characters.
2. Set it in your framework’s metadata mechanism (Next.js Metadata API, WordPress SEO plugin, Shopify page settings) so it is per-page, not hardcoded site-wide.

• Each page shows its own title in the browser tab.
• Re-scan: "Page title" flips to PASS.

• Don’t stuff keywords. The title is quoted verbatim in agent answers, and a keyword string reads as spam exactly where customers see it.
• Don’t reuse one title across all pages; identical names make pages indistinguishable in citations.

Time to first byte is how long your server thinks before it starts answering: the gap between an agent asking for the page and the first byte of HTML arriving. Yours crossed our threshold (under 200ms scores full marks, over 2 seconds fails).

Agents fetch with tight timeouts and many pages in parallel. A server that takes seconds to start answering gets cut off mid-queue, and a page that times out is a page that was never read. Speed here is not polish; it decides whether the content gets fetched at all.

1. Cache the HTML itself. Marketing and docs pages rarely change per visitor; serve them from a CDN or static cache so no application code runs per request.
2. If you are on serverless hosting, cold starts are a common cause: keep the function warm or pre-render the page.
3. Move slow work (database queries, third-party API calls) out of the first response; render the shell fast and fill personalised details after.

• Run: curl -o /dev/null -s -w "%{time_starttransfer}\n" https://yoursite.com and watch the number drop.
• Hit Re-scan above: "Time to first byte" improves a bucket at a time (under 500ms passes).

• Don’t answer fast with an empty shell that loads content by JavaScript. That trades this warning for the much worse "content requires JavaScript" failure, since most agents never run your scripts.
• Don’t special-case known crawler user agents onto a faster path. Serving different performance to different audiences is the pattern crawlers penalise when they detect it.

The thing you want people to do on this page (add to cart, book, subscribe) has to be a real element in the page code: a link with an address, or a button. On your page the words are there, but they are painted on. They live inside an image, or on a plain box styled to look like a button.

An agent working your page does not look at pixels. It reads the list of things it can click. A call to action drawn into an image is not on that list, so the agent scrolls past the exact thing you wanted it to press. In a controlled test, a button baked into an image was clicked zero times out of ten by every model tried, while the same button as a real element was clicked seven times out of ten.

1. Find the main call to action on this page and look at how it is built. In your browser, right-click it and choose Inspect.
2. If you see <img> or a <div> with a background image, replace it with a real <a href="..."> or <button> and put the words in as text.
3. If the design needs an image, keep the image inside the link or button and give the link an aria-label with the words: <a href="/cart" aria-label="Add to cart">.
4. An <a> tag with no href is not a link. Give it a real destination, or make it a <button>.

• View the page source (Ctrl+U) and search for the words of your call to action. They should appear as text, not only as an image filename.
• Try the page with a keyboard: press Tab. If focus never lands on your main action, an agent cannot reach it either.
• Re-scan: "Primary action is clickable" flips to PASS.

• Do not rely on alt text to make an image clickable. Alt text describes an image, it does not create a link, and in testing it did nothing for interaction.
• Do not add invented attributes like data-llm-description or data-ai-action. Those were tested and had no effect at all; use real HTML elements instead.
• Do not add a hidden duplicate link only agents can see. That is cloaking, it fails our coherence checks, and it is the pattern assistants are getting better at spotting.