Website review, no card needed

nutrilog.net logo

nutrilog.net website review

Visit site (opens in a new tab)Reviewed 8 November 202634 issues · 74 checks

This review found 34 issues worth fixing on nutrilog.net, 11 of them high impact, across 74 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 nutrilog.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix70
  • Use efficient cache lifetimes

    3.0 s · 1.2 MB

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

  • Render-blocking requests

    2.2 s

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

  • Improve image delivery

    600 ms · 429 KiB

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

  • Mobile performance score: 70

    70/100

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

  • Reduce unused CSS

    650 ms · 164 KiB

    About 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 650 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, ZenDesk and Google Analytics and others), adding 518 KiB and 521 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 316 KiB

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

  • 2 long tasks on the main thread

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

  • Google Tag Manager adds 257 ms

    257 ms

    Google Tag Manager costs a phone 257 ms of main-thread work and 181 KiB 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.

  • Minify JavaScript

    150 ms · 56 KiB

    56 KiB could be saved by minifying JavaScript.

  • Minify CSS

    33 KiB

    33 KiB could be saved by minifying CSS.

  • Document request latency

    14 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 KiB JavaScript that modern phones do not need.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 191 ms

    191 ms

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

Core Web Vitals

5 to fix68
  • Largest Contentful Paint: 6.0 s

    6.0 s

    Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PASSEZ PLUS DE TEMPS AVEC VOS PATIENTS, MOINS A FAIRE DES C…”.

  • Time to Interactive: 9.1 s

    9.1 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 3.5 s

    3.5 s

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

  • 6 images without width and height

    6 images 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.

2 checks passed
  • Total Blocking Time: 174 ms

    174 ms

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

  • Cumulative Layout Shift: 0.01

    0.01

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

Images and page weight

1 to fix93
  • 3 images below the first screen load straight away

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

  • 5 images in older formats

    5 images (485 KiB) 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.

  • About 0.4 g of CO₂ per visit

    0.43 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.6 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: 1.5 MB in 45 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 45 requests on a phone: images 760 KiB (15), scripts 548 KiB (14) and stylesheets 178 KiB (4). That is a lean page.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8592
  • 2 text elements with low contrast

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

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

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

  • No main landmark

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

  • 4 links without text

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 28 automated accessibility rules passed

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

SEO

4 to fixGoogle 9276
  • No meta description

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

  • Title is short (8 characters)

    Your title is only 8 characters: “Nutrilog”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 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 X (Twitter) card tag

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

  • 29 internal links, 5 external

    The homepage links to 29 pages on nutrilog.net and 5 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “PASSEZ PLUS DE TEMPS AVEC VOS PATIENTS,MOINS A FAIRE DES CALCULS”.

  • Canonical URL set

    The canonical URL is http://nutrilog.net/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at http://nutrilog.net/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://nutrilog.net/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 (437 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix48
  • 3 linked pages are broken

    Your homepage links to https://nutrilog.net/test-page, https://nutrilog.net/politique-de-confidentialite and https://nutrilog.net/en/politique-de-confidentialite, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page points its canonical at the homepage

    https://nutrilog.net/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 4 pages share 2 titles

    / and https://nutrilog.net/home all use the title “Nutrilog”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://nutrilog.net/home, https://nutrilog.net/diet-practice, https://nutrilog.net/epidemiology, https://nutrilog.net/ehealth, https://nutrilog.net/body-composition and https://nutrilog.net/about and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://nutrilog.net/support-nutrilog, https://nutrilog.net/support-online, https://nutrilog.net/mentions-legales and https://nutrilog.net/en/mentions-legales have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 internal pages checked

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

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 5696
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 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 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 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 411 words of copy

    The homepage carries about 411 words of visible text.

2 checks passed
  • Analytics in place

    Analytics detected: Google Analytics and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 nutrilog.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2022.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Team Blue Carrier Limited

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on nutrilog.net, including 14 speed issues, 4 SEO issues and 3 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