102walnut.com website review

About 507 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

Google Maps costs a phone 304 ms of main-thread work and 465 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.

6 third-party services load with your homepage (Google Maps, Google Tag Manager and Google Analytics and others), adding 632 KiB and 462 ms of main-thread time.

About 136 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 70 ms faster on a phone.

4 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).

4 long tasks block the main thread while loading, the longest for 103 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

1 image could be 64 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “102 WALNUT | Downtown Winona Historical Restoration with Mo…”.

The page becomes fully interactive after 12.5 s. Good is under 3.8 s.

The first text or image appears after 4.3 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.

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.

Your homepage downloads 2.2 MB in 100 requests on a phone: scripts 1.2 MB (74), images 749 KiB (9) and fonts 162 KiB (4). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.64 g of CO₂e: 76.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

9 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (2 elements).

Your meta description is only 12 characters: “#description”. 70 to 160 characters is enough to sell the click.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 16 pages on 102walnut.com and 7 external pages.

https://www.102walnut.com/home declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.102walnut.com/home all use the title “Office & Retail Space For Lease - 102 Walnut St Winona Minnesota”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.102walnut.com/author/6vbns has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.102walnut.com/about and https://www.102walnut.com/privacy-policy use the same meta description. A description written for each page earns more clicks.

https://www.102walnut.com/news, https://www.102walnut.com/about, https://www.102walnut.com/schedule-a-showing, https://www.102walnut.com/author/6vbns, https://www.102walnut.com/nosh-is-open and https://www.102walnut.com/estimated-opening-date-of-nosh-scratch-kitchen-pushed-back and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.102walnut.com/nosh-is-open and https://www.102walnut.com/home took over 3 s to send their HTML from our server.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

4 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 3 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 223 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before 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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.