Website review, no card needed

nomuz.net logo

nomuz.net website review

Visit site (opens in a new tab)Reviewed 12 November 202637 issues · 70 checks

This review found 37 issues worth fixing on nomuz.net, 14 of them high impact, across 70 checks. The most urgent: use efficient cache lifetimes. 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 nomuz.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix52
  • Use efficient cache lifetimes

    1.2 s · 268 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (268 KiB).

  • Improve image delivery

    150 ms · 7.9 MB

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

  • Reduce unused JavaScript

    900 ms · 172 KiB

    About 172 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google/Doubleclick Ads, adtrafficquality.google and Other Google APIs/SDKs and others), adding 8.3 MB and 149 ms of main-thread time.

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 8.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    450 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 5.0 s

    5.0 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Real-user TTFB: 3.6 s

    3.6 s

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

  • Cumulative Layout Shift: 1.001

    1.001

    The layout shifts by 1.001 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NameClub Discover high-value domains for your next business…”.

  • Time to Interactive: 6.6 s

    6.6 s

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

5 checks passed
  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.06

    0.06

    For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.

  • Speed Index: 3.0 s

    3.0 s

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • Total Blocking Time: 64 ms

    64 ms

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

Images and page weight

4 to fix28
  • 10 images over 500 KB

    10 images weigh 8.0 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 8.8 MB in 80 requests

    8.8 MB

    Your homepage downloads 8.8 MB in 80 requests on a phone: images 8.3 MB (24), scripts 405 KiB (28) and fonts 96 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    2.6 MB

    10 images are downloaded at several times the size a phone draws them, for example image_article_140_1.webp at 1,280 px wide, shown at 350 px. Resized copies would save about 2.6 MB.

  • 9 images below the first screen load straight away

    9 images further down the page (7.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.50 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9397
  • 5 text elements with low contrast

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

5 to fixGoogle 9272
  • No meta description

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

  • Title is short (21 characters)

    Your title is only 21 characters: “Computing | Dynaguide”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Canonical points to another host

    Your canonical URL points to dynaguide.com, not content.dynadot.com, so Google may credit that host instead.

  • Structured data has 1 problem

    Structured data found (WebPage and WebSite) but with 1 problem, for example “WebPage: url is not an absolute URL ("https://www.dynaguide.com/Technology & Computing/Computing")”.

  • No social preview image

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

  • 11 internal links, 0 external

    The homepage links to 11 pages on nomuz.net and 0 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Computing”.

  • 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://www.dynaguide.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 https://content.dynadot.com/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 (821 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 6 pages share a title

    /, https://content.dynadot.com/Technology%20&%20Computing, https://content.dynadot.com/Business%20and%20Finance, https://content.dynadot.com/Education, https://content.dynadot.com/Travel and https://content.dynadot.com/Entertainment all use the title “DynaGuide | Practical Guides on Everyday Topics | Dynaguide”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://content.dynadot.com/article/148, https://content.dynadot.com/all and https://content.dynadot.com/privacy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    /, https://content.dynadot.com/Technology%20&%20Computing, https://content.dynadot.com/Business%20and%20Finance, https://content.dynadot.com/Education, https://content.dynadot.com/Travel and https://content.dynadot.com/Entertainment use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://content.dynadot.com/Business%20and%20Finance, https://content.dynadot.com/Education and https://content.dynadot.com/Entertainment have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://content.dynadot.com/article/148, https://content.dynadot.com/all and https://content.dynadot.com/contact 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.

  • 11 internal pages checked

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

4 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9289
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Hydration completed but contains mismatches.”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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 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.

  • 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 849 words of copy

    The homepage carries about 849 words of visible text.

1 checks passed
  • 1 call to action

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

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

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at nomuz.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on nomuz.net, including 14 speed issues, 5 SEO issues 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
nomuz.net website review: scores and fixes | Programmable