64custom.com website review

• Google's speed test didn't respond

  Google's speed test didn't respond for this site, so speed and Core Web Vitals are not measured here. Your full playbook measures them.

Not measured in this review.

• About 0.00 g of CO₂ per visit

  0.00 g

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

• No main landmark

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

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• No meta description

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

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• Title is short (12 characters)

  Your title is only 12 characters: “64custom.com”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No structured data

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

• No canonical URL

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

• No social preview image

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

• No XML sitemap

  No XML sitemap at https://64custom.com/sitemap.xml, so Google discovers your pages only by following links.

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No favicon declared

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

• No X (Twitter) card tag

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

• No Organization structured data

  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.

• No llms.txt

  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.

• 1 JavaScript error while loading

  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 404 ()”.

• http:// does not redirect

  http://64custom.com does not redirect to https, so some visitors land on the insecure version.

• No HSTS header

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

• No Content-Security-Policy

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

• No clickjacking protection

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

• No X-Content-Type-Options

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

• No Referrer-Policy

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

• No Permissions-Policy

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

• No security.txt

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

• No CAA record

  64custom.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.

• DNSSEC is off

  64custom.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 call to action on the first screen

  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 calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• No social proof

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

• No direct contact details

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

• Only about 1 words

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

• No form on the homepage

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

• No risk reducer

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

• No DMARC policy

  64custom.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.

• No DKIM key on the usual selectors

  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 score: 35/100

  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 consent tool detected

  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.

• 1 other company contacted

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