Website review, no card needed
presscafeftworth.com website review
Visit site (opens in a new tab)Reviewed 25 October 202629 issues · 66 checks
This review found 29 issues worth fixing on presscafeftworth.com, 6 of them high impact, across 66 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.2 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 941 ms |
| Jul 18, 2026 | 945 ms |
| Jul 25, 2026 | 914 ms |
| Aug 1, 2026 | 998 ms |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 954 ms |
| Sep 5, 2026 | 981 ms |
| Sep 12, 2026 | 947 ms |
| Sep 19, 2026 | 981 ms |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 62 ms |
| May 9, 2026 | 62 ms |
| May 16, 2026 | 62 ms |
| May 23, 2026 | 63 ms |
| May 30, 2026 | 63 ms |
| Jun 6, 2026 | 67 ms |
| Jun 13, 2026 | 64 ms |
| Jun 20, 2026 | 62 ms |
| Jun 27, 2026 | 62 ms |
| Jul 4, 2026 | 61 ms |
| Jul 11, 2026 | 62 ms |
| Jul 18, 2026 | 62 ms |
| Jul 25, 2026 | 62 ms |
| Aug 1, 2026 | 62 ms |
| Aug 8, 2026 | 62 ms |
| Aug 15, 2026 | 62 ms |
| Aug 22, 2026 | 62 ms |
| Aug 29, 2026 | 59 ms |
| Sep 5, 2026 | 57 ms |
| Sep 12, 2026 | 56 ms |
| Sep 19, 2026 | 56 ms |
| Sep 26, 2026 | 59 ms |
| Oct 3, 2026 | 61 ms |
| Oct 10, 2026 | 63 ms |
| Oct 17, 2026 | 63 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.7 s
1.3 s
2.0 s
2.6 s
3.3 s
3.9 s
4.6 s
5.2 s
Speed
Render-blocking requests
3.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Use efficient cache lifetimes
300 ms · 1.4 MB32 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Mobile performance score: 79
79/100Your mobile performance score is 79 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Improve image delivery
652 KiB13 images could be 652 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 third-party services on the page
6 third-party services load with your homepage (Google Maps, Google Tag Manager and Google CDN and others), adding 723 KiB and 570 ms of main-thread time.
Reduce unused JavaScript
330 ms · 302 KiBAbout 302 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 330 ms faster on a phone.
Google Maps adds 340 ms
340 msGoogle Maps costs a phone 340 ms of main-thread work and 473 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 458 ms of it running JavaScript. That is comfortably low.
Core Web Vitals
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 10.3 s
10.3 sThe page becomes fully interactive after 10.3 s. Good is under 3.8 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Press Cafe - Ft. Worth Logo”. Most of its time is resource load delay (2.5 s).
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 62 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 63 ms
63 msReal visitors wait 63 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: 445 ms
445 msReal visitors wait 445 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 122 ms
122 msScripts block the page for only 122 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 55 requests
2.1 MBYour homepage downloads 2.1 MB in 55 requests on a phone: images 1.3 MB (25), scripts 653 KiB (20) and fonts 59 KiB (4). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 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.
4 images below the first screen load straight away
4 images further down the page (652 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.9 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 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (30 elements)
All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
26 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 29 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://www.presscafeftworth.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at presscafeftworth.com/robots.txt, the first file search crawlers ask for.
Only 2 internal links
The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.
One H1 headline
Your <h1> is empty.
3 checks passed
Meta description: 114 characters
Your meta description is 114 characters: “Press Cafe - Ft. Worth - A modern cafe setting serving American classics and local favorites in Fort Worth, Texas.”.
Title: 62 characters
Your title is a healthy 62 characters: “Press Cafe - Ft. Worth | Casual American Cafe | Fort Worth, TX”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.presscafeftworth.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (425 words), so crawlers that don't run JavaScript still read it.
Best practices
5 small tap targets
5 of 8 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 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.
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.
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.
About 418 words of copy
The homepage carries about 418 words of visible text.
6 checks passed
1 call to action
The homepage has 1 call to action, for example “Reserve Now”.
Social proof on the page
Social proof on the homepage: 11 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 5 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
8 other companies contacted
Loading the homepage contacts 8 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 presscafeftworth.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 Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on presscafeftworth.com, including 12 speed issues, 6 SEO issues and 2 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.