Website review, no card needed
tpnevents.com website review
Visit site (opens in a new tab)Reviewed 18 October 202630 issues · 67 checks
This review found 30 issues worth fixing on tpnevents.com, 10 of them high impact, across 67 checks. The most urgent: reduce unused JavaScript. 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
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.9 s
Speed
Reduce unused JavaScript
1.7 s · 337 KiBAbout 337 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
1.3 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 130 KiBAbout 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Squarespace, Hubspot and sqspcdn.com and others), adding 1.3 MB and 698 ms of main-thread time.
Use efficient cache lifetimes
600 ms · 125 KiB7 files are served with short cache lifetimes, so returning visitors download them again (125 KiB).
Legacy JavaScript
600 ms · 118 KiBPolyfills for old browsers add 118 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.
Squarespace adds 558 ms
558 msSquarespace costs a phone 558 ms of main-thread work and 934 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.
Improve image delivery
300 ms · 47 KiB1 image could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 670 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 245 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 85 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 49 ms
49 msYour server sent the HTML in 49 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.7 s
10.7 sYour largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TPN EXISTS TO CREATE SPACES AND REASONS FOR HUMANS TO CONNE…”.
First Contentful Paint: 6.5 s
6.5 sThe first text or image appears after 6.5 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.7 s
10.7 sThe page becomes fully interactive after 10.7 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 304 ms
304 msScripts block taps and scrolling for 304 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.41 g of CO₂e: 49.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.5 MB in 68 requests
1.5 MBYour homepage downloads 1.5 MB in 68 requests on a phone: scripts 1,003 KiB (45), stylesheets 167 KiB (11) and other files 120 KiB (4). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (10 characters)
Your title is only 10 characters: “TPN Events”. Between 30 and 65 characters leaves room to say what you do and for whom.
7 H1 headlines
There are 7 <h1> headlines (“TPN exists to create spaces and reasons for human…”, “Our Services” and “STRATEGY”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/67f824e83d9ccd03a9e…”.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
32 internal links, 3 external
The homepage links to 32 pages on tpnevents.com and 3 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.tpnevents.com/.
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://www.tpnevents.com/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://www.tpnevents.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
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 (379 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.tpnevents.com/case-studies, which answers with an error. Visitors hit a dead end and search engines drop it.
7 pages without a meta description
https://www.tpnevents.com/strategy, https://www.tpnevents.com/design, https://www.tpnevents.com/production, https://www.tpnevents.com/technology, https://www.tpnevents.com/our-work and https://www.tpnevents.com/stories and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.tpnevents.com/technology and https://www.tpnevents.com/stories have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.tpnevents.com/technology, https://www.tpnevents.com/stories and https://www.tpnevents.com/contact-7-2-1 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.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 7 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/67f824e83d9ccd03a9e2b6e2/48/5c5a…”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 299 words of copy
The homepage carries about 299 words of visible text.
2 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Contact” and “LEARN MORE”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads HubSpot (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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
14 other companies contacted
Loading the homepage contacts 14 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 tpnevents.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
- Squarespace
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 tpnevents.com, including 16 speed issues, 5 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.