Website review, no card needed

devgenes.com logo

devgenes.com website review

Visit site (opens in a new tab)Reviewed 9 November 202614 issues · 73 checks

This review found 14 issues worth fixing on devgenes.com, 2 of them high impact, across 73 checks. The most urgent: no DMARC policy. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of devgenes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. devgenes.com at 0.4 s0.4 s
  2. devgenes.com at 0.8 s0.8 s
  3. devgenes.com at 1.1 s1.1 s
  4. devgenes.com at 1.5 s1.5 s
  5. devgenes.com at 1.9 s1.9 s
  6. devgenes.com at 2.3 s2.3 s
  7. devgenes.com at 2.6 s2.6 s
  8. devgenes.com at 3.0 s3.0 s

devgenes.com does not allow embedding, so this is Google's rendering of the page.

Speed

100
  • Render-blocking requests

    150 ms

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

  • Improve image delivery

    65 KiB

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

  • Chained critical requests

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.1 s

    A phone's processor spends 0.1 s on main-thread work while loading, 5 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

1 to fix100
  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    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.

6 checks passed
  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “I built and sold Nureply. Now I operate eight live iOS apps…”.

  • Speed Index: 0.8 s

    0.8 s

    Visually, the page fills in at 0.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

1 to fix90
  • 1 image far larger than shown

    29 KiB

    1 image is downloaded at several times the size a phone draws it, for example onur-warehouse.jpg at 1,280 px wide, shown at 350 px. Resized copies would save about 29 KiB.

  • 1 image in older formats

    1 image (88 KiB) is 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.

  • About 0.04 g of CO₂ per visit

    0.04 g

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

2 checks passed
  • Page weight: 133 KiB in 4 requests

    133 KiB

    Your homepage downloads 133 KiB in 4 requests on a phone: images 89 KiB (1), fonts 35 KiB (1) and stylesheets 6 KiB (1). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 0 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 10 internal links, 5 external

    The homepage links to 10 pages on devgenes.com and 5 external pages.

7 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Onur Genes builds, buys, grows and sells software products, operates eight iOS apps and runs niche commerce businesses …”.

  • One H1 headline

    Your main headline reads: “I build things,buy some,and sell a few.”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Onur Genes — Founder, app operator, serial experimenter”.

  • Canonical URL set

    The canonical URL is https://onurgenes.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://onurgenes.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (238 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example /projects.html, whose canonical is /projects. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    /contact.html has 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.

  • 4 internal pages checked

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

6 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

  • Every page has a meta description

    All 4 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    7 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

2 to fix88
  • 1 broken external link

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

  • No HSTS header

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

  • No security.txt

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

6 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (onurgenes.com).

  • Valid certificate (69 days left)

    The certificate from Google Trust Services · WE1 verifies for devgenes.com and is valid for another 69 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://devgenes.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

Domain and trust

  • No CAA record

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

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

2 checks passed
  • Domain is 12 years old

    12 years

    onurgenes.com was registered in Sep 2014 through NameCheap, Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Sep 2028

    onurgenes.com is registered until Sep 2028.

Content and conversion

4 to fix58
  • 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 analytics detected

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

  • 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 238 words

    The homepage has only about 238 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.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

Email authentication

3 to fix25
  • No DMARC policy

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

  • SPF does not block other senders (no all)

    Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=_spf.yandex.net”.

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

Privacy and tracking

  • 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 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 14 issues on devgenes.com, including 1 speed issue, 1 SEO issue and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25