codemanbd.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 7.1 s

  7.1 s

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

• Real-user FCP: 5.0 s

  5.0 s

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

• Real-user TTFB: 3.4 s

  3.4 s

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

• Real-user INP: 432 ms

  432 ms

  Real visitors wait 432 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Tap response (INP) got 66% slower for real visitors

  +66%

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

• Largest content (LCP) got 134% slower for real visitors

  +134%

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

• Page weight: 13.1 MB

  13.1 MB

  Your homepage downloads 13.1 MB on a phone, 10.3 MB of it images (79%). Under 2 MB keeps phones on slow connections fast.

• 30 images in older formats

  30 images (3.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  Elements (5)

• 3 images far larger than shown

  259 KiB

  3 images are downloaded at several times the size a phone draws them, for example Payoneer_logo.svg-scaled.png at 2,560 px wide, shown at 67 px. Resized copies would save about 259 KiB.

  Elements (3)

• 5 images below the first screen load straight away

  5 images further down the page (342 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (5)

• About 3.7 g of CO₂ per visit

  3.73 g

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

• Certain ARIA roles must contain particular children (3 elements)

  Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  Elements (3)

• 3 tap targets too small

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

  Elements (3)

• Links look like plain text

  1 link inside paragraphs relies on colour alone to stand out.

  Elements (1)

• All page content should be contained by landmarks (166 elements)

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

  Elements (3)

• No main landmark

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

  Elements (1)

• 23 links without text

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

  Elements (3)

• Headings skip levels

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

  View sourceElements (2)

• 104 internal links, 28 external

  The homepage links to 104 pages on codemanbd.com and 28 external pages.

• Opted out of AI training for 5 crawlers

  robots.txt blocks GPTBot, 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.

• 1 link to non-canonical URLs

  Your homepage links to 1 page by a URL that isn't its canonical one, for example /ethical-hacking-cyber-security, whose canonical is /ethical-hacking. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (1)

• 1 page without an H1

  /success-stories has no <h1> headline, so visitors and search engines get no clear main topic.

• 7 pages slow to respond

  /courses, /ai-agent-and-automation, /wordpress-and-ecommerce, /elementor-and-shopify, /wix-and-webflow and /fiverr-crash and 1 other took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 20 small tap targets

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getContext')”.

• 3 links through redirect chains

  3 links go through two or more redirects, for example https://www.google.com/local/business/11096359875436726515/customers/reviews.

• No security.txt

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

• DNSSEC is off

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

• About 1,119 words of copy

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

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• DMARC is monitor-only (p=none)

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

• 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: 60/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.

• 5 trackers load before any consent

  5

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

• 23 cookies set on arrival

  23

  Opening the homepage sets 23 cookies (measured from a US location before any click).

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

• 15 other companies contacted

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