robblake.net website review

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

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

5 third-party services load with your homepage (Tumblr, Google/Doubleclick Ads and WordPress and others), adding 1.3 MB and 618 ms of main-thread time.

Tumblr costs a phone 494 ms of main-thread work and 1,000 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.

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

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

1 image could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “I'm a technology entrepreneur, Java developer and SaaS cons…”.

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

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

Visually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 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.

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

10 frames have no title, so screen-reader users cannot tell what they contain.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is only 9 characters: “Rob Blake”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 38 pages on robblake.net and 9 external pages.

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 ClaudeBot, Google-Extended, Applebot-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, which the crawlers above handle.

/rss has no <title>, so Google invents the link text in results.

/ and /post/31854258074/im-increasingly-viewing-twitter-and-joinappnet all use the title “Rob Blake”. Search engines can't tell which page to show for a search, so each competes with the others.

/rss has no meta description, so Google writes the search snippet from whatever text it finds.

/post/31875460413/read-my-crap-or-why-asymmetric-social-media-is, /post/31854258074/im-increasingly-viewing-twitter-and-joinappnet, /post/28976133221/unified-error-handling-with-apache-2-tomcat-7-and, /post/26350897979/java-using-amazon-ses-to-send-an-email-with, /post/18945733710/using-a-pem-private-key-and-ssl-certificate-with and /post/8183156536/jpa-ensuring-versioning-of-entities-when-using and 3 others use the same meta description. A description written for each page earns more clicks.

/rss and /archive have no <h1> headline, so visitors and search engines get no clear main topic.

/post/31854258074/im-increasingly-viewing-twitter-and-joinappnet, /about, /ask and /archive 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.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 resources load over plain http on your https page (for example http://drnicwilliams.com/external/CodeHighlighter/styles.css); browsers block or warn about them.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

1 link go through two or more redirects, for example http://docs.jboss.org/hibernate/core/3.3/reference/en/html/mapping.html.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

robblake.net 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.

robblake.net'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.

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

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 3,038 words of visible text.

DMARC is set to p=none, so mail pretending to be robblake.net is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Comscore and Google Ads (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.

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