codehappier.com website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

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.07 g of CO₂e: 8.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

Elements with visible text labels do not have matching accessible names. (5 elements).

Your title is only 17 characters: “Code Happier Blog”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 65 characters: “A blog to share my experience building and scaling a SaaS product”. 70 to 160 characters is enough to sell the click.

The homepage links to 30 pages on codehappier.com and 7 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.

/blog, /tags, /tags/career-development, /tags/leadership, /tags/people and /tags/development and 4 others use the same meta description. A description written for each page earns more clicks.

/tags, /tags/career-development, /tags/leadership, /tags/people, /tags/scale and /tags/team-building and 2 others 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 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

19 of 39 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 “Loading the script 'https://cloud.umami.is/script.js' violates the following Content Security Policy directive: "script…”.

Chrome logged issues while loading the page (“Content security policy”).

1 link to other sites is dead, for example https://www.linkedin.com/in/tannerhallman/ (999).

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

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

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.

The homepage has only about 190 words of visible text; thin pages give Google and first-time buyers little to go on.

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

codehappier.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

codehappier.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

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.

codehappier.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

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.

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