contentcolumn.com website review

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

About 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

About 1.2 MB of JavaScript is downloaded but never used on this page.

11 images could be 703 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

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

2 third-party services load with your homepage (YouTube and Google Fonts), adding 114 KiB and 26 ms of main-thread time.

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.

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

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

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

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

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

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.

Your homepage downloads 3.6 MB in 400 requests on a phone: scripts 2.0 MB (100), images 870 KiB (11) and fonts 495 KiB (228). Under 2 MB keeps phones on slow connections fast.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 42 pages on contentcolumn.com and 0 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.

/services, /saas-content-strategy, /saas-content-writing, /saas-seo, /saas-content-audit and /saas-link-building and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/services, /saas-content-strategy, /saas-content-audit, /saas-public-relations and /blog-2 have no <h1> headline, so visitors and search engines get no clear main topic.

/services, /saas-content-writing, /saas-seo, /saas-content-audit, /saas-link-building and /saas-public-relations took over 3 s to send their HTML from our server.

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

6 images failed to load on a phone, for example https://contentcolumn.com/.

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://contentcolumn.com/' was loaded over HTTPS, but requested an insecure font 'http://c…”.

Chrome logged issues while loading the page (“Mixed content”).

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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.

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.

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

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

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

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.

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

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.

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