mesamoldremediation.com, read 2 days ago. Back to the report

98 to 100 in 4 steps

Do them in this order. Each step says what to change, on which pages, and what it adds. Hand the whole plan to your agent, or work through it yourself.

9898 nownow981992top 0.1%9931004full marks

Now #2,048 of 263,895Step 2 top 0.1%Step 4 full marks

Worked out from this read, with every step before it done. A score says pages are well formed. It does not say an assistant cites the site.

The steps

Each is one change across the pages named. When one is live, read the site again and mttr marks it done.

  1. 1

    Compress pages

    Under a point

    Turn on gzip or Brotli for HTML on the server or CDN.

    Once, for the whole site

  2. 2

    Speed up the server

    +1 point, to 99, and #180, 1,868 places up, and into the top 0.1%

    Cache pages or speed up the server. Crawlers give a slow site fewer visits.

    Once, for the whole site

  3. 3

    Add an llms.txt

    Under a point

    Add /llms.txt: a short plain text map of the site for assistants. Its effect is unproven, so treat it as cheap insurance.

    Once, for the whole site

  4. 4

    Link straight to the final address

    +1 point, to 100, and full marks

    Point links and the sitemap at the final address, not at one that redirects.

    1 page

    See the pages
    • /contact-us
1 more, to tidy up after 100
  1. 5

    Set a share image

    Under a point

    Set og:image so links to the page carry a picture.

    1 page

    See the pages
    • /contact-us

What else the read found

Half its pages take over 947 ms to start answering, past the 800 ms a crawler is patient with. Caching or a faster server helps every page at once. One fetch a page, the way a crawler sees it.

  • /1.2 s
  • /services1.0 s
  • /about-us882 ms
  • /contact-us508 ms

Fastest: /contact-us, 508 ms. Heaviest: the home page, 128 KB.

Read from its home page’s code and the headers its server sent. A tool that loads later, or only on other pages, is not seen here.

  • WordPressPlatform
  • ApacheServer
  • Google reCAPTCHALibrary
  • jQueryLibrary
  • Google FontsFonts
  • Font AwesomeFonts

From the structured data on its home page, as the site says it: an Organization named Mesa Mold Remediation - Mold Containment & Removal. mttr does not check the profiles it names.

  • Yelpmesa-mold-remediation-mold-containment-and-removal-mesa
  • FacebookMesa-Mold-Remediation-Mold-Containment-and-Removal-103626795705336
pages with strong signs
2
hidden characters
5
chat, markdown or placeholders left in
0
dashes per 1,000 words
2.8
  • / hidden characters a reader cannot see
  • /services hidden characters a reader cannot see

A sign is not proof. Hidden characters can carry a watermark or instructions meant for an AI, and they come off with a clean copy of the text.

  • / passes every rule1 page
  • /contact-us fails 2: Link straight to the final address and Set a share image1 page
  • /about-us passes every rule1 page
  • /services passes every rule1 page

Rather go through these with one of our experts? Book a strategy session

Fix mesamoldremediation.com with your agent

Your agent makes the fixes. mttr checks each one. Free.

In the site’s repositorynpx skills add subinternal/mttr
Then tell your agentCheck mesamoldremediation.com with mttr and fix what’s worth the most.

Claude Code, Codex, Cursor or any agent that reads AGENTS.md.

Claude Code, onceclaude mcp add --transport http mttr https://mttr.si/mcp
It needs a free key
Another agent
Read it againChanged something? A site is read at most once every ten minutes.