Website review, no card needed
stockmag.net website review
Visit site (opens in a new tab)Reviewed 8 November 202621 issues · 61 checks
This review found 21 issues worth fixing on stockmag.net, 4 of them high impact, across 61 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.7 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
archive.org adds 104 ms
104 msarchive.org costs a phone 104 ms of main-thread work and 583 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.
Reduce unused CSS
150 ms · 57 KiBAbout 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
186 KiB15 files are served with short cache lifetimes, so returning visitors download them again (186 KiB).
3 third-party services on the page
3 third-party services load with your homepage (archive.org, Cloudflare and brohgoslot.com), adding 595 KiB and 116 ms of main-thread time.
Improve image delivery
168 KiB4 images could be 168 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
44 KiBAbout 44 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
10 KiBPolyfills 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.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 115 ms of it running JavaScript. That is comfortably low.
Server response: 89 ms
89 msYour server sent the HTML in 89 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 17.1 s
17.1 sVisually, the page fills in at 17.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
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.
4 checks passed
Largest Contentful Paint: 2.2 s
2.2 sYour largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Le Magazine des Gestionnaires de Stock”.
Time to Interactive: 2.2 s
2.2 sThe page is fully interactive after 2.2 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.18 g of CO₂e: 21.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 649 KiB in 87 requests
649 KiBYour homepage downloads 649 KiB in 87 requests on a phone: images 404 KiB (18), scripts 175 KiB (16) and other files 38 KiB (43). That is a lean page.
Accessibility
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
51 text elements with low contrast
51 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
6 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 8 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Article, NewsMediaOrganization, Organization and Person) but with 1 problem, for example “Organization: url points at a different host (https://web.archive.org/web/20240913024428/https://st…”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://stockmag.net/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at stockmag.net/robots.txt, the first file search crawlers ask for.
54 internal links, 6 external
The homepage links to 54 pages on stockmag.net and 6 external pages.
4 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Le magazine des gestionnaires de stocks, des logiciels de gestion de stock sur le Cloud, en mode SaaS, avec le TOP 6 de…”.
One H1 headline
Your main headline reads: “Le Magazine des Gestionnaires de Stock”.
Title: 49 characters
Your title is a healthy 49 characters: “Le Magazine des Gestionnaires de stock - StockMag”.
Canonical URL set
The canonical URL is https://stockmag.net/.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://stockmag.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.
Other pages
15 linked pages hidden from search
https://stockmag.net/web, https://stockmag.net/web/20240913024428*/https://stockmag.net, https://stockmag.net/web/20240913024428/http://web.archive.org/screenshot/https://stockmag.net, https://stockmag.net/sortly, https://stockmag.net/meilleurs-logiciels-gestion-stock and https://stockmag.net/booqable and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages share a title
https://stockmag.net/web, https://stockmag.net/web/20240913024428*/https://stockmag.net, https://stockmag.net/web/20240913024428/http://web.archive.org/screenshot/https://stockmag.net, https://stockmag.net/sortly, https://stockmag.net/meilleurs-logiciels-gestion-stock and https://stockmag.net/booqable and 9 others all use the title “Site ready”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://stockmag.net/web, https://stockmag.net/web/20240913024428*/https://stockmag.net, https://stockmag.net/web/20240913024428/http://web.archive.org/screenshot/https://stockmag.net, https://stockmag.net/sortly, https://stockmag.net/meilleurs-logiciels-gestion-stock and https://stockmag.net/booqable and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
4 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.
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
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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
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.
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 321 words of copy
The homepage carries about 321 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 stockmag.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on stockmag.net, including 5 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.