Website review, no card needed
tollwayplaza.com website review
Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 74 checks
This review found 33 issues worth fixing on tollwayplaza.com, 10 of them high impact, across 74 checks. The most urgent: improve image delivery. 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
79CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
1.9 s · 2.4 MB11 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.6 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 76
76/100Your mobile performance score is 76 (desktop: 97). Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Maps, Other Google APIs/SDKs and Google Fonts and others), adding 3.4 MB and 317 ms of main-thread time.
Google Maps adds 315 ms
315 msGoogle Maps costs a phone 315 ms of main-thread work and 464 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.
Cloudinary adds 0 ms
0 msCloudinary costs a phone 0 ms of main-thread work and 2.9 MB 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.
Reduce unused JavaScript
234 KiBAbout 234 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 76 ms. During a long task the page ignores taps.
Document request latency
53 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Use efficient cache lifetimes
21 KiB3 files are served with short cache lifetimes, so returning visitors download them again (21 KiB).
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 231 ms of it running JavaScript. That is comfortably low.
Server response: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tollway Plaza I - 16000 North Dallas Parkway”.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
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.
3 checks passed
Speed Index: 2.9 s
2.9 sVisually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 39 ms
39 msScripts block the page for only 39 ms while loading. Good is under 200 ms.
Images and page weight
2 images over 500 KB
2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
511 KiB3 images are downloaded at several times the size a phone draws them, for example gljuhbsxt94orz7h0inn at 1,500 px wide, shown at 390 px. Resized copies would save about 511 KiB.
Page weight: 3.5 MB in 33 requests
3.5 MBYour homepage downloads 3.5 MB in 33 requests on a phone: images 2.9 MB (13), scripts 446 KiB (13) and HTML 81 KiB (2). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (985 KiB) is 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.
About 1.0 g of CO₂ per visit
0.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
38 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: 38 passed and 4 failed. 2 mores 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 structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
19 internal links, 26 external
The homepage links to 19 pages on tollwayplaza.com and 26 external pages.
6 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “View property details, location and nearby places of interest for Tollway Plaza I - 16000 North Dallas Parkway”.
Title: 56 characters
Your title is a healthy 56 characters: “Tollway Plaza I - 16000 North Dallas Parkway, Dallas, TX”.
Canonical URL set
The canonical URL is https://tollwayplaza.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://tollwayplaza.com/tollwayplaza_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://tollwayplaza.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 (418 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://tollwayplaza.com/building/tollway-plaza-i-16000-north-dallas-parkway-dallas-tx/brochure has no <title>, so Google invents the link text in results.
2 pages point its canonical at the homepage
https://tollwayplaza.com/availability and https://tollwayplaza.com/contact declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://tollwayplaza.com/availability and https://tollwayplaza.com/contact all use the title “Tollway Plaza I - 16000 North Dallas Parkway, Dallas, TX”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://tollwayplaza.com/building/tollway-plaza-i-16000-north-dallas-parkway-dallas-tx/brochure has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://tollwayplaza.com/availability and https://tollwayplaza.com/contact use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://tollwayplaza.com/building/tollway-plaza-i-16000-north-dallas-parkway-dallas-tx/brochure, https://tollwayplaza.com/availability and https://tollwayplaza.com/contact have no <h1> headline, so visitors and search engines get no clear main topic.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
2 checks passed
Linked pages load
All 3 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
14 small tap targets
14 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://marketplace-assets.market-prd.prd.us-east-1.vts.com/assets/microsites-6beaeaed9ba9…”.
1 checks passed
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 403 words of copy
The homepage carries about 403 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact” and “Inquire”.
5 calls to action
The homepage has 5 calls to action, for example “Contact” and “Inquire”.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 2 mores (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
19 other companies contacted
Loading the homepage contacts 19 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 tollwayplaza.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on tollwayplaza.com, including 10 speed issues, 2 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.