Website review, no card needed
sushihouse.by website review
Visit site (opens in a new tab)Reviewed 18 November 202630 issues · 74 checks
This review found 30 issues worth fixing on sushihouse.by, 12 of them high impact, across 74 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 132 ms |
| Jun 6, 2026 | 124 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 112 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 111 ms |
| Aug 1, 2026 | 110 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 105 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 102 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 107 ms |
| Oct 17, 2026 | 111 ms |
| Oct 24, 2026 | 114 ms |
| Oct 31, 2026 | 115 ms |
| Nov 7, 2026 | 115 ms |
| Nov 14, 2026 | 115 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
Speed
Render-blocking requests
1.0 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,685 HTML elements
The page has 4,685 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 309 KiBAbout 309 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 393 ms. During a long task the page ignores taps.
bitrix24.by adds 216 ms
216 msbitrix24.by costs a phone 216 ms of main-thread work and 716 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 · 226 KiBAbout 226 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.
2 third-party services on the page
2 third-party services load with your homepage (bitrix24.by and foodpicasso.com), adding 980 KiB and 216 ms of main-thread time.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Improve image delivery
63 KiB6 images could be 63 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
16 KiB1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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: 259 ms
259 msYour server sent the HTML in 259 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Заказывайте любимые роллы в Sushi House и получайте скидку …”.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 475 ms
475 msScripts block taps and scrolling for 475 ms in total while the page loads. Good is under 200 ms.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 710 ms
710 msReal visitors wait 710 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 132 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.054
0.054The layout barely moves while loading (CLS 0.054, good is under 0.1).
Images and page weight
About 0.6 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 66.5 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: 2.0 MB in 96 requests
2.0 MBYour homepage downloads 2.0 MB in 96 requests on a phone: scripts 733 KiB (26), fonts 478 KiB (5) and stylesheets 285 KiB (37). That is a lean page.
Accessibility
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
417 text elements with low contrast
417 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 (2 elements)
All page content should be contained by landmarks: 2 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.
1 checks passed
8 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 11 WCAG 2.2 A/AA and best-practice rules on the phone render: 8 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
223 internal links, 6 external
The homepage links to 223 pages on sushihouse.by and 6 external pages.
8 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “Закажите суши, роллы, сеты, WOK и другие блюда SUSHI HOUSE в Минске. Оформляйте доставку или самовывоз онлайн.”.
One H1 headline
Your main headline reads: “Суши и роллы с доставкой в Минске”.
Title: 45 characters
Your title is a healthy 45 characters: “Доставка суши и роллов в Минске | SUSHI HOUSE”.
Canonical URL set
The canonical URL is https://sushihouse.by/.
Structured data in place
Structured data found: MobileApplication.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://sushihouse.by/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://sushihouse.by/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.
1 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.
Other pages
11 linked pages are broken
Your homepage links to https://sushihouse.by/sertificates, https://sushihouse.by/promotions, https://sushihouse.by/minsk/s/sale, https://sushihouse.by/minsk/s/street-rolls, https://sushihouse.by/minsk/s/pop-ap-rolly_351 and https://sushihouse.by/minsk/s/rolls and 5 others, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://sushihouse.by/about_us and https://sushihouse.by/delivery have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://sushihouse.by/about_us, whose canonical is https://sushihouse.by/minsk/about_us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://sushihouse.by/feedback has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://sushihouse.by/about_us, https://sushihouse.by/delivery, https://sushihouse.by/feedback and https://sushihouse.by/minsk/s/set 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 200 found) and read each the way a search engine does.
3 checks passed
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.
1 checks passed
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.
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.
Only about 5 words
The homepage has only about 5 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 3 trust badges.
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 sushihouse.by, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Business Network Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on sushihouse.by, including 12 speed issues, 1 SEO issue and 5 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.