Website

Turn a site-wide speed crawl into developer tickets by template

Crawls the whole site, pulls the full URL list for every speed-related issue, groups pages by template, audits sample URLs per template with resource-level detail, and delivers a sorted developer ticket list with honest page counts.

When to use it

When your whole site has speed or layout-shift problems and you need to hand developers a clear, prioritised list of what to fix.

What you get

A developer ticket list grouped by page template, with affected page counts, example URLs, the files involved, recommended fixes and effort, sorted by impact.

Does it change anything in my account?

No. The assistant only reads your data and reports back.

Works with

SEO Intelligence

Fill in before sending

[domain][max pages]
Use my Opus Growth connection for this. If you cannot see the tool you need, search among the Opus Growth tools (with search_tools if it is in your list); if you cannot reach the tools at all, do not guess, tell me. First, check my SEO add-on history for a crawl of [domain] that can still be reused for free. If one exists, reuse it. If not, remind me that a site-wide crawl uses SEO add-on credits and wait for my go-ahead before you start a crawl of up to [max pages] pages. The crawl runs in the background: start it, then check back with the task id every minute or two until the summary is ready. From the crawl summary, take every issue type that relates to speed or layout stability, if it appears in the data. Examples: large page size, slow load time, redirect chains, render-blocking resources, oversized images, images without width/height. Use the issue names exactly as the summary returns them. For each of these issues, pull the full URL list (page through it), not just the first 5 examples. Group the affected URLs by template or path pattern, for example /blog/, /product/, /category/ and landing pages. For each template, count the affected pages per issue from those full lists. Then pick the worst URL in each template. Before running technical audits, tell me how many you plan to run (they also use add-on credits) and wait for my OK. On each worst URL, run a technical audit and a mobile Core Web Vitals check with the resource lists switched on. Use the resource lists to name the actual files: which stylesheets and scripts block rendering, how many bytes of unused CSS and JS, which images are oversized or not in a modern format, the total request count and the LCP element. To see whether an audit finding is template-wide or a one-off, run the free mobile Core Web Vitals check (with resource lists) on 2 more URLs from the same template. Counting rule: only issues that come from the crawl's URL lists get a page count. For issues found only in the audits, write "confirmed on X of 3 sampled URLs" instead of a page count. Do not extrapolate a page count from one URL. Deliver a ticket list with these columns: template, issue, affected pages (or sample ratio), example URL, files or elements involved, recommended fix, effort (S/M/L), metric it should improve (LCP, CLS, INP/TBT, page weight). Sort by affected pages × severity; for sample-only issues use the sample ratio and mark them as such. This is read-only. Do not change anything on the site.

Related searches

These prompts work best when your AI assistant is connected to your accounts with Opus Growth.

Connect your accounts free

More prompts

WebsiteChanges after your approvalLive demo

Build an editorial expert site with a guides section and author schema

Has your assistant build an expert's site with a magazine-cover home page, long-form guides and an author profile. Serif typography, Article and Person schema and dated, sourced articles produce a publication people read and AI answers can cite.

When to use itWhen you are a consultant, specialist or one-person knowledge business and want your site to read like a publication that shows your expertise through writing, not like a brochure.

SEO Intelligence, Search Console
WebsiteChanges after your approvalLive demo

Build a heritage family business site with a classic look and modern standards

Has your assistant build a site in the spirit of an old label and shop sign for a producer in its third generation, framed and with a paper texture. The look is old, the build is new: mobile first, JavaScript-free, self-hosted fonts, WebP, Product and HowTo schema.

When to use itWhen you sell a craft passed down through generations, such as Turkish delight, olive oil, cheese or copperware, and want a classic look that carries that history without giving up speed or accessibility.

SEO Intelligence, Search Console
WebsiteChanges after your approvalLive demo

Build a Swiss-minimal law or accounting firm site with strong trust signals

Has your assistant build a still firm site on a strict grid, with hierarchy carried by a single type family. It puts the trust signals a YMYL field needs on the page: practitioner profiles, a dated and sourced guidance note, wording that respects professional advertising rules, and Person schema.

When to use itWhen a law, accounting or similar professional practice needs a site that looks serious and plain, stays within professional advertising rules and proves its expertise.

SEO Intelligence, Search Console
WebsiteChanges after your approvalLive demo

Build a JavaScript-free multi-page corporate site and deliver it at 100

Has your assistant build a still, fast and accessible site for corporate work such as architecture, engineering or consulting. Menu and footer are static HTML, fonts and CSS are self-hosted, and every page is measured before hand-over.

When to use itWhen a corporate business needs a multi-page site where speed and accessibility matter more than decoration, with no animation and no JavaScript.

SEO Intelligence, Search Console