Website review, no card needed

adulisrestaurant.com logo

adulisrestaurant.com website review

Visit site (opens in a new tab)Reviewed 17 November 202642 issues · 74 checks

This review found 42 issues worth fixing on adulisrestaurant.com, 19 of them high impact, across 74 checks. The most urgent: improve image delivery. 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 adulisrestaurant.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adulisrestaurant.com at 0.8 s0.8 s
  2. adulisrestaurant.com at 1.5 s1.5 s
  3. adulisrestaurant.com at 2.3 s2.3 s
  4. adulisrestaurant.com at 3.1 s3.1 s
  5. adulisrestaurant.com at 3.9 s3.9 s
  6. adulisrestaurant.com at 4.6 s4.6 s
  7. adulisrestaurant.com at 5.4 s5.4 s
  8. adulisrestaurant.com at 6.2 s6.2 s

Speed

13 to fix63
  • Improve image delivery

    19.8 s · 6.2 MB

    4 images could be 6.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 19.8 s faster on a phone.

  • Use efficient cache lifetimes

    14.2 s · 4.4 MB

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

  • Render-blocking requests

    1.2 s

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

  • 3,196 HTML elements

    The page has 3,196 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Mobile performance score: 63

    63/100

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

  • Reduce initial server response time

    973 ms

    Reduce initial server response time. Google estimates savings of 973 ms on a phone.

  • Document request latency

    950 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (etsy.com, Google Tag Manager and Sentry and others), adding 1.4 MB and 649 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 602 KiB

    About 602 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.

  • Reduce unused CSS

    450 ms · 69 KiB

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

  • etsy.com adds 362 ms

    362 ms

    etsy.com costs a phone 362 ms of main-thread work and 918 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.

  • Google Tag Manager adds 137 ms

    137 ms

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

  • Server response: 1.1 s

    1.1 s

    Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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 checks passed
  • Main-thread work: 1.3 s

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

Core Web Vitals

6 to fix63
  • Largest Contentful Paint: 23.7 s

    23.7 s

    Your largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “GADUNSLOT 🧠 Situs Slot Bonus New Member 100 TO X 10 Bebas …”.

  • Time to Interactive: 23.7 s

    23.7 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 13 images without width and height

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

  • Total Blocking Time: 208 ms

    208 ms

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix25
  • Page weight: 7.7 MB in 45 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 45 requests on a phone: images 6.3 MB (11), scripts 1.2 MB (18) and fonts 89 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.1 MB

    1 image is downloaded at several times the size a phone draws it, for example logo-gds.webp at 932 px wide, shown at 120 px. Resized copies would save about 1.1 MB.

  • 1 image in older formats

    1 image (2.5 MB) is 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 2.2 g of CO₂ per visit

    2.19 g

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

1 checks passed
  • Images load when needed

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

Accessibility

9 to fixGoogle 8187
  • ARIA attributes must conform to valid values (9 elements)

    ARIA attributes must conform to valid values: 9 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 tap targets too small

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “GADUNSLOT 🧠 Situs Slot Bonus New Member 100 TO X 10 Bebas IP Gampang Menang Terbaru”.

  • Meta description is long (251 characters)

    Your meta description is 251 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 110 internal links, 7 external

    The homepage links to 110 pages on adulisrestaurant.com and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “GADUNSLOT 🧠 Situs Slot Bonus New Member 100 TO X 10 Bebas IP Gampang Menang Terbaru”.

  • Canonical URL set

    The canonical URL is https://sanmateodeeptissue.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, Product, SoftwareApplication and VideoObject.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://sanmateodeeptissue.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing 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://sanmateodeeptissue.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (3,617 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://sanmateodeeptissue.com/guest/favorites, https://sanmateodeeptissue.com/gift-mode, https://sanmateodeeptissue.com/help/article/5307, https://sanmateodeeptissue.com/legal/ip, https://sanmateodeeptissue.com/legal/sellers and https://sanmateodeeptissue.com/legal/prohibited and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=20013160&tm=gtm002&Ver=2&mid=83566620-5703-483f-a524-0bc4c9f6ef7d&bo=1&sid=f1e52f90e28211f180b4239719b6dd62&vid=f1e560a0e28211f18aada91cda75c0b8&vids=1&msclkid=N&pi=91.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected identifier 'New'”.

2 checks passed
  • Tap targets are thumb-sized

    54 of 67 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • A 10-field form

    Your longest form asks for 10 fields (0 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 2,018 words of copy

    The homepage carries about 2,018 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

3 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Learn more about this item”, “View additional shop policies” and “Following Follow shop”.

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks, a star rating and “10.5K reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 13 other companies contacted

    Loading the homepage contacts 13 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 adulisrestaurant.com, 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
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on adulisrestaurant.com, including 19 speed issues, 2 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