Website review, no card needed

dotnet-sas.net logo

dotnet-sas.net website review

Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 79 checks

This review found 32 issues worth fixing on dotnet-sas.net, 6 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Real-visitor load time (LCP)75th percentile, phones
2.2 s1.4 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.8 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
252 ms213 msMay 23Nov 7236 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026235 ms
May 30, 2026236 ms
Jun 6, 2026236 ms
Jun 13, 2026236 ms
Jun 20, 2026236 ms
Jun 27, 2026241 ms
Jul 4, 2026245 ms
Jul 11, 2026245 ms
Jul 18, 2026247 ms
Jul 25, 2026244 ms
Aug 1, 2026239 ms
Aug 8, 2026238 ms
Aug 15, 2026236 ms
Aug 22, 2026235 ms
Aug 29, 2026243 ms
Sep 5, 2026233 ms
Sep 12, 2026225 ms
Sep 19, 2026222 ms
Sep 26, 2026222 ms
Oct 3, 2026218 ms
Oct 10, 2026217 ms
Oct 17, 2026217 ms
Oct 24, 2026220 ms
Oct 31, 2026229 ms
Nov 7, 2026236 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of dotnet-sas.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dotnet-sas.net at 1.6 s1.6 s
  2. dotnet-sas.net at 3.2 s3.2 s
  3. dotnet-sas.net at 4.8 s4.8 s
  4. dotnet-sas.net at 6.4 s6.4 s
  5. dotnet-sas.net at 8.0 s8.0 s
  6. dotnet-sas.net at 9.6 s9.6 s
  7. dotnet-sas.net at 11.2 s11.2 s
  8. dotnet-sas.net at 12.8 s12.8 s

Speed

7 to fix65
  • Mobile performance score: 65

    65/100

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

  • Font display

    800 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).

  • Use efficient cache lifetimes

    673 KiB

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

  • Reduce unused JavaScript

    594 KiB

    About 594 KiB of JavaScript is downloaded but never used on this page.

  • Improve image delivery

    250 ms · 267 KiB

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

  • 5 long tasks on the main thread

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

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    57 KiB

    About 57 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Sentry), adding 1 KiB and 0 ms of main-thread time.

1 checks passed
  • Server response: 313 ms

    313 ms

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

Core Web Vitals

8 to fix33
  • 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.

  • Speed Index: 10.5 s

    10.5 s

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

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Real-user INP: 285 ms

    285 ms

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

  • Real-user CLS: 0.11

    0.11

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

  • Total Blocking Time: 497 ms

    497 ms

    Scripts block taps and scrolling for 497 ms in total while the page loads. Good is under 200 ms.

  • Largest Contentful Paint: 3.7 s

    3.7 s

    Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fiche de paie”. Most of its time is resource load delay (2.8 s).

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 799 ms

    799 ms

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

  • Cumulative Layout Shift: 0.097

    0.097

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

Images and page weight

1 to fix85
  • Page weight: 2.1 MB in 144 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 144 requests on a phone: scripts 1.1 MB (113), images 747 KiB (20) and HTML 105 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.60 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8991
  • 13 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (3 elements)

    Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 15 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.

  • 33 tap targets too small

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • Title is long (76 characters)

    Your title is 76 characters, so Google will cut it off around 60: “Logiciel de paie : Créez 1 fiche de paie en 2 Minutes + DSN - Fiche-paie.net”.

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 46 internal links, 2 external

    The homepage links to 46 pages on dotnet-sas.net and 2 external pages.

5 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Logiciel de paie pour créer une fiche de paie en ligne en 2 minutes. DSN incluse + Journal de paie + Mises à jour régle…”.

  • One H1 headline

    Your main headline reads: “Fiche de paie”.

  • Canonical URL set

    The canonical URL is https://www.fiche-paie.net/.

  • 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.fiche-paie.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://www.fiche-paie.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 (481 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.fiche-paie.net/acces-compte is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.fiche-paie.net/acces-compte has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages slow to respond

    https://www.fiche-paie.net/page/faq, https://www.fiche-paie.net/page/la-cotisation-intemperies-btp-principes-et-taux-en-vigueur, https://www.fiche-paie.net/page/absence-non-remuneree-quelle-gestion-en-paie and https://www.fiche-paie.net/page/fiche-paienet-rejoint-indy-annonce-rachat took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9691
  • 2 small tap targets

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

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

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

2 to fix70
  • 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 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 355 words of copy

    The homepage carries about 355 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: PostHog.

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

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 dotnet-sas.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

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 32 issues on dotnet-sas.net, including 15 speed issues, 4 SEO issues and 2 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