jiminny.com website review

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

About 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 53 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

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

8 third-party services load with your homepage (website-files.com, openai.com and Omniconvert and others), adding 929 KiB and 511 ms of main-thread time.

website-files.com costs a phone 209 ms of main-thread work and 657 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 1,734 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 200 ms. During a long task the page ignores taps.

About 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Desktop scores 88 but mobile only 53. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

Your largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 177 ms to 310 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 325 ms in total while the page loads. Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image is downloaded at several times the size a phone draws it, for example 698f5ff86cb3a95610ee5f3c_hero-mockup.avif at 2,500 px wide, shown at 487 px. Resized copies would save about 35 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 71 elements on the page fail this check, rated moderate by axe-core.

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

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 134 pages on jiminny.com and 14 external pages.

Your robots.txt shuts out Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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 /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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

Large scripts ship without source maps.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

jiminny.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

jiminny.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

The homepage carries about 1,131 words of visible text.

DMARC is set to p=none, so mail pretending to be jiminny.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 6 cookies (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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.