Website review, no card needed
alto-shaam.com website review
Visit site (opens in a new tab)Reviewed 30 October 202651 issues · 90 checks
This review found 51 issues worth fixing on alto-shaam.com, 22 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 151 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 175 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 186 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 182 ms |
| Jul 4, 2026 | 185 ms |
| Jul 11, 2026 | 175 ms |
| Jul 18, 2026 | 168 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 144 ms |
| Sep 5, 2026 | 199 ms |
| Sep 12, 2026 | 239 ms |
| Sep 19, 2026 | 241 ms |
| Sep 26, 2026 | 225 ms |
| Oct 3, 2026 | 188 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 129 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
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.6 s
4.2 s
Speed
Reduce unused JavaScript
3.1 s · 2.0 MBAbout 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Wistia adds 1.8 s
1.8 sWistia costs a phone 1.8 s of main-thread work and 10.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
2.9 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Reduce unused CSS
2.3 s · 490 KiBAbout 490 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Google CDN adds 2.5 s
2.5 sGoogle CDN costs a phone 2.5 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Improve image delivery
1.1 s · 1.4 MB11 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 18.1 s
A phone's processor spends 18.1 s on main-thread work while loading, 11.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 24
24/100Your mobile performance score is 24. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Wistia and Google Tag Manager and others), adding 13.8 MB and 6.1 s of main-thread time.
Font display
950 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).
Google Tag Manager adds 886 ms
886 msGoogle Tag Manager costs a phone 886 ms of main-thread work and 534 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
750 ms · 143 KiB143 KiB could be saved by minifying JavaScript.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 442 ms. During a long task the page ignores taps.
Other Google APIs/SDKs adds 381 ms
381 msOther Google APIs/SDKs costs a phone 381 ms of main-thread work and 70 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.
LiveChat adds 191 ms
191 msLiveChat costs a phone 191 ms of main-thread work and 364 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.
1,693 HTML elements
The page has 1,693 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
113 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Use efficient cache lifetimes
48 KiB10 files are served with short cache lifetimes, so returning visitors download them again (48 KiB).
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 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.
1 checks passed
Server response: 82 ms
82 msYour server sent the HTML in 82 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 4.5 s
4.5 sReal visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PIONEERS IN FOODSERVICE EQUIPMENT INNOVATION”.
Speed Index: 21.7 s
21.7 sVisually, the page fills in at 21.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 77.2 s
77.2 sThe page becomes fully interactive after 77.2 s. Good is under 3.8 s.
Total Blocking Time: 4.4 s
4.4 sScripts block taps and scrolling for 4.4 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.117
0.117The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 136 ms
136 msReal visitors wait 136 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 151 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 23.6 MB in 160 requests
23.6 MBYour homepage downloads 23.6 MB in 160 requests on a phone: images 7.4 MB (21), media 5.8 MB (5) and other files 5.5 MB (53). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.
8 images below the first screen load straight away
8 images further down the page (6.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
11 images in older formats
11 images (1.7 MB) 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.
2 images far larger than shown
99 KiB2 images are downloaded at several times the size a phone draws them, for example Dash-In_Success-Story_Alto-Shaam.png at 1,400 px wide, shown at 390 px. Resized copies would save about 99 KiB.
About 6.7 g of CO₂ per visit
6.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.68 g of CO₂e: 802.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Alto-Shaam Commercial Kitchen Equipment | Restaurant & Foodservice”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
22 links with vague text
22 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
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.
91 internal links, 5 external
The homepage links to 91 pages on alto-shaam.com and 5 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Alto-Shaam offers innovative commercial kitchen appliances and equipment, along with top-notch customer support for ins…”.
One H1 headline
Your main headline reads: “Origin™ Multi-Cook Convection Ovens”.
Canonical URL set
The canonical URL is https://www.alto-shaam.com/en.
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.alto-shaam.com/en/sitemap.xml.
AI search readiness
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.alto-shaam.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 (1,126 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
https://www.alto-shaam.com/en, https://www.alto-shaam.com/fr, https://www.alto-shaam.com/es and https://www.alto-shaam.com/de all use the title “Alto-Shaam Commercial Kitchen Equipment | Restaurant & Foodservice”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.alto-shaam.com/en/quick-ship has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.alto-shaam.com/fr, https://www.alto-shaam.com/es and https://www.alto-shaam.com/de use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 60 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.
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 15 pages that loaded have a <title>.
Best practices
73 small tap targets
73 of 101 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
A 22-field form
Your longest form asks for 22 fields (21 required). Every extra field lowers completion.
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 664 words of copy
The homepage carries about 664 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request Service” and “How to Buy”.
23 calls to action
The homepage has 23 calls to action, for example “Request Service”, “How to Buy” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 4 of them by other companies (measured from a US location before any click).
20 other companies contacted
Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: TrustArc
A consent management tool (TrustArc) loads with the page.
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 alto-shaam.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on alto-shaam.com, including 27 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.