Website review, no card needed
twincities.com website review
Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 95 checks
This review found 39 issues worth fixing on twincities.com, 20 of them high impact, across 95 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
Site score
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 3.8 s |
| Nov 7, 2026 | 3.7 s |
| Nov 14, 2026 | 3.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 339 ms |
| Jun 6, 2026 | 438 ms |
| Jun 13, 2026 | 452 ms |
| Jun 20, 2026 | 461 ms |
| Jun 27, 2026 | 429 ms |
| Jul 4, 2026 | 338 ms |
| Jul 11, 2026 | 328 ms |
| Jul 18, 2026 | 330 ms |
| Jul 25, 2026 | 345 ms |
| Aug 1, 2026 | 340 ms |
| Aug 8, 2026 | 334 ms |
| Aug 15, 2026 | 328 ms |
| Aug 22, 2026 | 330 ms |
| Aug 29, 2026 | 319 ms |
| Sep 5, 2026 | 319 ms |
| Sep 12, 2026 | 319 ms |
| Sep 19, 2026 | 306 ms |
| Sep 26, 2026 | 304 ms |
| Oct 3, 2026 | 299 ms |
| Oct 10, 2026 | 296 ms |
| Oct 17, 2026 | 291 ms |
| Oct 24, 2026 | 304 ms |
| Oct 31, 2026 | 323 ms |
| Nov 7, 2026 | 338 ms |
| Nov 14, 2026 | 361 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.6 s
1.2 s
1.8 s
2.4 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Reduce unused JavaScript
4.5 s · 2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Use efficient cache lifetimes
4.2 s · 2.4 MB174 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
Render-blocking requests
5.6 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.
Main-thread work: 18.9 s
A phone's processor spends 18.9 s on main-thread work while loading, 13.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
cloudfront.net adds 1.2 s
1.2 scloudfront.net costs a phone 1.2 s of main-thread work and 79 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 17
17/100Your mobile performance score is 17. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Osano CMP and others), adding 2.2 MB and 4.0 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 2.8 s. During a long task the page ignores taps.
Osano CMP adds 561 ms
561 msOsano CMP costs a phone 561 ms of main-thread work and 122 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/Doubleclick Ads adds 400 ms
400 msGoogle/Doubleclick Ads costs a phone 400 ms of main-thread work and 279 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.
1,526 HTML elements
The page has 1,526 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
200 ms · 123 KiBPolyfills for old browsers add 123 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Improve image delivery
250 ms · 48 KiB3 images could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Reduce unused CSS
11 KiBAbout 11 KiB of CSS is downloaded but never applied on this page.
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: 32 ms
32 msYour server sent the HTML in 32 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.4 s
4.4 sReal visitors wait 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.60
0.60For real visitors the layout shifts by 0.60 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 21.9 s
21.9 sYour largest element takes 21.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Minnesota Vikings head coach Kevin O'Connell speaks with qu…”.
Speed Index: 23.3 s
23.3 sVisually, the page fills in at 23.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 69.1 s
69.1 sThe page becomes fully interactive after 69.1 s. Good is under 3.8 s.
Total Blocking Time: 4.0 s
4.0 sScripts block taps and scrolling for 4.0 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 6.1 s
6.1 sThe first text or image appears after 6.1 s on a phone. Good is under 1.8 s.
Real-user INP: 399 ms
399 msReal visitors wait 399 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.193
0.193The layout shifts by 0.193 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 339 ms to 361 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.5 MB in 1,175 requests
9.5 MBYour homepage downloads 9.5 MB in 1,175 requests on a phone: scripts 5.6 MB (168), images 2.7 MB (397) and other files 542 KiB (480). Under 2 MB keeps phones on slow connections fast.
About 2.7 g of CO₂ per visit
2.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.71 g of CO₂e: 324.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail 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.
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
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Twin Cities” and “”). One clear main headline is easier for people and search engines.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
235 internal links, 32 external
The homepage links to 235 pages on twincities.com and 32 external pages.
6 checks passed
Meta description: 130 characters
Your meta description is 130 characters: “St. Paul news -- including crime, politics, education, business, sports, entertainment and things to do -- from the Pio…”.
Title: 54 characters
Your title is a healthy 54 characters: “St. Paul News, Sports and Things To Do | Pioneer Press”.
Canonical URL set
The canonical URL is https://www.twincities.com/.
Structured data in place
Structured data found: LocalBusiness and NewsMediaOrganization.
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.twincities.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No llms.txt
There is no https://www.twincities.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.
2 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 (2,319 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a meta description
https://www.twincities.com/news/politics, https://www.twincities.com/news/health, https://www.twincities.com/news/national, https://www.twincities.com/news/world, https://www.twincities.com/news/environment and https://www.twincities.com/local-news and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://www.twincities.com/news/education took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 142 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://rtb.mfadsrvr.com/sync?ssp=revcontent&ssp_user_id=4f115814101d4022996129b7a9c22b52&gpp=DBACOe~CQt0_oAQt0_oAEX1mAENC4FgAAAAAEPgACiQAAAUlgIgAVAA4ACQAGgARQAmABoAEcAK0AZYBAACDgLzAaKA5YB8YFJQAAAA.IK.
34 third-party cookies
34 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 4 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'querySelector')”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
104 of 109 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
About 1,337 words of copy
The homepage carries about 1,337 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Subscribe Now” and “Subscribe”.
11 calls to action
The homepage has 11 calls to action, for example “Subscribe Now”, “Subscribe” and “Sign Up”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 4 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
45 cookies set on arrival
45Opening the homepage sets 45 cookies (measured from a US location before any click).
97 other companies contacted
Loading the homepage contacts 97 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) loads with the page.
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 twincities.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
- React
- Analytics
- Google Tag Manager
- Hosting
- WordPress.com
Company
- Founded
- 1849
- Headquarters
- Saint Paul
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on twincities.com, including 25 speed issues, 1 SEO issue and 1 conversion gap. 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.