Website review, no card needed
thisislandscape.com website review
Visit site (opens in a new tab)Reviewed 30 October 202630 issues · 74 checks
This review found 30 issues worth fixing on thisislandscape.com, 10 of them high impact, across 74 checks. The most urgent: page weight: 56.1 MB in 91 requests. 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.1 s |
| May 23, 2026 | 5.1 s |
| May 30, 2026 | 4.5 s |
| Jun 20, 2026 | 3.5 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
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.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Render-blocking requests
1.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Improve image delivery
2.6 MB15 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 84
84/100Your mobile performance score is 84. 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 (Cookiebot, Google Tag Manager and cloudfront.net and others), adding 6.3 MB and 248 ms of main-thread time.
Use efficient cache lifetimes
750 ms · 35 KiB3 files are served with short cache lifetimes, so returning visitors download them again (35 KiB).
Vimeo adds 0 ms
0 msVimeo costs a phone 0 ms of main-thread work and 6.0 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.
Reduce unused JavaScript
90 KiBAbout 90 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
14 KiBAbout 14 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 522 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 30.0 s
30.0 sVisually, the page fills in at 30.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 52.1 s
52.1 sThe page becomes fully interactive after 52.1 s. Good is under 3.8 s.
Largest Contentful Paint: 2.8 s
2.8 sYour largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Landscape Logo”. Most of its time is resource load delay (1.2 s).
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.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
Largest content (LCP) got 34% faster for real visitors
-34%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.1 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 85 ms
85 msScripts block the page for only 85 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 56.1 MB in 91 requests
56.1 MBYour homepage downloads 56.1 MB in 91 requests on a phone: media 35.4 MB (15), images 19.4 MB (55) and scripts 1.2 MB (11). Under 2 MB keeps phones on slow connections fast.
15 images over 500 KB
15 images weigh 11.5 MB together. On a phone connection a single image that size takes seconds.
30 images in older formats
30 images (14.7 MB) are 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.
2 images below the first screen load straight away
2 images further down the page (68 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 15.9 g of CO₂ per visit
15.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 15.90 g of CO₂e: 1908.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 5 failed. 1 more 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.
Title is short (19 characters)
Your title is only 19 characters: “Landing - Landscape”. Between 30 and 65 characters leaves room to say what you do and for whom.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
43 internal links, 2 external
The homepage links to 43 pages on thisislandscape.com and 2 external pages.
6 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “Landscape is a boutique brand strategy and design studio shaping structure and surface in service of social good.”.
Canonical URL set
The canonical URL is https://thisislandscape.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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://thisislandscape.com/sitemap_index.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://thisislandscape.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 (325 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://thisislandscape.com/news, https://thisislandscape.com/work, https://thisislandscape.com/events, https://thisislandscape.com/contact, https://thisislandscape.com/projects/modal and https://thisislandscape.com/projects/journ and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://thisislandscape.com/contact and https://thisislandscape.com/jobs have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://thisislandscape.com/contact has 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.
5 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.
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
11 small tap targets
11 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
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.
Thin social proof
Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 318 words of copy
The homepage carries about 318 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”, “Start a Project” and “Subscribe”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 thisislandscape.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
- jQuery
- Analytics
- Google Analytics
- Hosting
- Google Cloud
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 thisislandscape.com, including 11 speed issues, 3 SEO issues and 2 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.