WPIntell

Source evidence

Error Message ‘Something went wrong. Please try again…’

Five Star Restaurant Reservations – WordPress Booking Plugin · support · 2026-03-19T15:35:00+00:00

complaintsentiment
highseverity
0.78relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 25 rows with source links

12.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Rickp01 unresolved
Hi Guys, My client is getting an intermittent error: ‘Something went wrong. Please try again and, if the issue persists, please contact us.’ on his booking page. https://oldbutcherswinecellar.co.uk/wine-bar-bookings/ My client says: ‘When it comes up with the error message if you refresh the page the error goes away. The problem is that customers don’t do that they just send us angry messages that they can’t book!!!’ Screen shot of the error here: https://oldbutcherswinecellar.co.uk/wp-content/uploads/2026/03/Screenshot-2026-02-17-at-18.53.09.png Any ideas? Thanks – Richard The page I need help with: [ log in to see the link] Hi Richard, By any chance, are you using a caching plugin? If so, could you clear your cache and see if that makes a difference? This reply was modified 2 months, 1 week ago by jaysupport . Thanks for looking! WordPress Hosting. Chat GPT search: From the HTML you shared, there is no clear evidence of a traditional WordPress caching plugin (like WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.). However, there is strong evidence of WordPress.com / Jetpack edge caching . Here are the key indicators. 1️⃣ WordPress.com / Jetpack platform caching This line is the giveaway: /wp-content/mu-plugins/wpcomsh/jetpack_vendor/ wpcomsh = WordPress.com hosting environment That means the site is very likely running on WordPress.com Business / VIP style infrastructure where caching is handled automatically at the platform level. These platforms use: edge caching object caching CDN caching asset concatenation All done without a visible caching plugin . 2️⃣ Static asset bundling (another caching signal) You also have URLs like: /_static/??-eJyVjMEKgCAQRH8o… That format is typical of WordPress.com asset concatenation / caching , where multiple CSS files are bundled and cached. This again confirms platform-level optimization rather than a plugin . 3️⃣ WordPress.com CDN for images Your schema shows images loading from: https://i0.wp.com/ i0.wp.com is the Jetpack / WordPress.com CDN . That means: images are cached globally resized dynamically served via CDN 4️⃣ Jetpack is installed You also have: /wp-content/plugins/jetpack/ Jetpack often provides: image CDN lazy loading asset optimization site accelerator caching ✅ Conclusion The site does have caching , but it is: Platform-level caching from WordPress.com + Jetpack CDN NOT a WordPress caching plugin. This reply was modified 2 months, 1 week ago by Rickp01 .

Comments

2 shown
jaysupport 2026-03-19T18:53:00+00:00

Hi Richard, By any chance, are you using a caching plugin? If so, could you clear your cache and see if that makes a difference? This reply was modified 2 months, 1 week ago by jaysupport .

Rickp01 2026-03-20T09:00:00+00:00

Thanks for looking! WordPress Hosting. Chat GPT search: From the HTML you shared, there is no clear evidence of a traditional WordPress caching plugin (like WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.). However, there is strong evidence of WordPress.com / Jetpack edge caching . Here are the key indicators. 1️⃣ WordPress.com / Jetpack platform caching This line is the giveaway: /wp-content/mu-plugins/wpcomsh/jetpack_vendor/ wpcomsh = WordPress.com hosting environment That means the site is very likely running on WordPress.com Business / VIP style infrastructure where caching is handled automatically at the platform level. These platforms use: edge caching object caching CDN caching asset concatenation All done without a visible caching plugin . 2️⃣ Static asset bundling (another caching signal) You also have URLs like: /_static/??-eJyVjMEKgCAQRH8o… That format is typical of WordPress.com asset concatenation / caching , where multiple CSS files are bundled and cached. This again confirms platform-level optimization rather than a plugin . 3️⃣ WordPress.com CDN for images Your schema shows images loading from: https://i0.wp.com/ i0.wp.com is the Jetpack / WordPress.com CDN . That means: images are cached globally resized dynamically served via CDN 4️⃣ Jetpack is installed You also have: /wp-content/plugins/jetpack/ Jetpack often provides: image CDN lazy loading asset optimization site accelerator caching ✅ Conclusion The site does have caching , but it is: Platform-level caching from WordPress.com + Jetpack CDN NOT a WordPress caching plugin. This reply was modified 2 months, 1 week ago by Rickp01 .