Website review, no card needed
pitajungle.com website review
Visit site (opens in a new tab)Reviewed 4 November 202621 issues · 77 checks
This review found 21 issues worth fixing on pitajungle.com, 6 of them high impact, across 77 checks. The most urgent: 2 text elements with low contrast. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 943 ms |
| May 30, 2026 | 925 ms |
| Jun 6, 2026 | 924 ms |
| Jun 13, 2026 | 923 ms |
| Jun 20, 2026 | 933 ms |
| Jun 27, 2026 | 947 ms |
| Jul 4, 2026 | 967 ms |
| Jul 11, 2026 | 973 ms |
| Jul 18, 2026 | 998 ms |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 71 ms |
| May 23, 2026 | 71 ms |
| May 30, 2026 | 71 ms |
| Jun 6, 2026 | 71 ms |
| Jun 13, 2026 | 73 ms |
| Jun 20, 2026 | 73 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 73 ms |
| Jul 11, 2026 | 72 ms |
| Jul 18, 2026 | 74 ms |
| Jul 25, 2026 | 75 ms |
| Aug 1, 2026 | 77 ms |
| Aug 8, 2026 | 77 ms |
| Aug 15, 2026 | 77 ms |
| Aug 22, 2026 | 78 ms |
| Aug 29, 2026 | 78 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 79 ms |
| Oct 3, 2026 | 79 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 78 ms |
| Oct 24, 2026 | 77 ms |
| Oct 31, 2026 | 78 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
Improve image delivery
500 ms · 233 KiB16 images could be 233 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
3 third-party services on the page
3 third-party services load with your homepage (Aggregate Knowledge, Adobe TypeKit and FontAwesome CDN), adding 145 KiB and 0 ms of main-thread time.
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.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Main-thread work: 0.2 s
A phone's processor spends 0.2 s on main-thread work while loading, 44 ms of it running JavaScript. That is comfortably low.
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide Background”.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 71 ms to 78 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 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: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 605 ms
605 msReal visitors wait 605 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 3.6 s
3.6 sThe page is fully interactive after 3.6 s.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Speed Index: 1.2 s
1.2 sVisually, the page fills in at 1.2 s (Speed Index), inside the 3.4 s “good” threshold.
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
1 image over 500 KB
25PJC_GazpachoPromo_Digital_Hompage.png weighs 743 KiB. On a phone connection a single image that size takes seconds.
Page weight: 2.6 MB in 46 requests
2.6 MBYour homepage downloads 2.6 MB in 46 requests on a phone: images 2.4 MB (39), fonts 144 KiB (6) and HTML 79 KiB (1). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.2 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 below the first screen load straight away
2 images further down the page (49 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 90.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
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.
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 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No XML sitemap
No XML sitemap at https://pitajungle.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at pitajungle.com/robots.txt, the first file search crawlers ask for.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
89 internal links, 42 external
The homepage links to 89 pages on pitajungle.com and 42 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Pita Jungle is a healthy restaurant specializing in Greek, Mediterranean, Lebanese, Middle Eastern, vegetarian and vega…”.
Title: 57 characters
Your title is a healthy 57 characters: “Healthy Mediterranean Restaurant in Arizona | Pita Jungle”.
Canonical URL set
The canonical URL is https://pitajungle.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (488 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pitajungle.com/llms.txt (1 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without an H1
https://pitajungle.com/menu/wood-fired-pizzas and https://pitajungle.com/menu/seasonal-kitchen-crafts-medmosaic have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://pitajungle.com/menu/wood-fired-pizzas has 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 32 found) and read each the way a search engine does.
6 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 12 pages that loaded have a meta description.
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 12 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Only about 232 words
The homepage has only about 232 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “ORDER ONLINE” and “ORDER CATERING”.
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “ORDER ONLINE” and “ORDER CATERING”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
3 other companies contacted
Loading the homepage contacts 3 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 pitajungle.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
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Matomo
- 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 pitajungle.com, including 2 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.