grrrow.me website review

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

A phone's processor spends 9.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (posthog.com, Cloudflare CDN and emergent.sh and others), adding 494 KiB and 552 ms of main-thread time.

posthog.com costs a phone 523 ms of main-thread work and 259 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 2,148 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

6 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.

7 files are served with short cache lifetimes, so returning visitors download them again (175 KiB).

About 155 KiB of JavaScript is downloaded but never used on this page.

4 images could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 26 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

18 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

Visually, the page fills in at 18.7 s (Speed Index). Good is under 3.4 s.

The layout shifts by 0.273 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The page becomes fully interactive after 6.4 s. Good is under 3.8 s.

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Indianapolis scanner traffic, as it happens.”. Most of its time is element render delay (11.6 s).

The first text or image appears after 1.8 s on a phone. Good is under 1.8 s.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 images (134 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.19 g of CO₂e: 22.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA commands must have an accessible name: 600 elements on the page fail this check, rated serious by axe-core.

370 tap targets are too small or too close together to hit reliably with a finger.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

12 visible links have no text or label, so screen readers cannot say where they go.

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at http://grrrow.me/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at grrrow.me/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 20 pages on grrrow.me and 0 external pages.

A phone browser shows 774 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://grrrow.me/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/, https://grrrow.me/feed, https://grrrow.me/imaps, https://grrrow.me/about, https://grrrow.me/contact and https://grrrow.me/feed/indianapolisindiana and 3 others all use the title “ALLCALL — The city moves fast. Stay ahead.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://grrrow.me/staging.html, https://grrrow.me/alerts.html and https://grrrow.me/privacy.html have no meta description, so Google writes the search snippet from whatever text it finds.

https://grrrow.me/feed, https://grrrow.me/imaps, https://grrrow.me/about, https://grrrow.me/contact, https://grrrow.me/feed/indianapolisindiana and https://grrrow.me/feed/chicagoillinois and 2 others use the same meta description. A description written for each page earns more clicks.

https://grrrow.me/feed, https://grrrow.me/imaps, https://grrrow.me/about, https://grrrow.me/contact, https://grrrow.me/feed/indianapolisindiana and https://grrrow.me/feed/chicagoillinois and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://grrrow.me/transcripts, https://grrrow.me/staging.html, https://grrrow.me/alerts.html and https://grrrow.me/privacy.html have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://grrrow.me/privacy.html, https://grrrow.me/feed/indianapolisindiana, https://grrrow.me/feed/chicagoillinois and https://grrrow.me/feed/dallastexas took over 3 s to send their HTML from our server.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

601 of 672 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

2 images are served at too low a resolution for sharp phone screens.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 774 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.