Website review, no card needed
nakdesignstrategies.com website review
Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 77 checks
This review found 32 issues worth fixing on nakdesignstrategies.com, 9 of them high impact, across 77 checks. The most urgent: page weight: 49.8 MB in 104 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
76CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.7 s
3.4 s
5.1 s
6.8 s
8.5 s
10.2 s
11.9 s
13.6 s
Speed
Render-blocking requests
1.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Improve image delivery
24.1 MB12 images could be 24.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 77
77/100Your mobile performance score is 77 (desktop: 65). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 196 KiBAbout 196 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Reduce unused CSS
300 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 288 KiB and 171 ms of main-thread time.
Minify JavaScript
150 ms · 6 KiB6 KiB could be saved by minifying JavaScript.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 245 ms of it running JavaScript. That is comfortably low.
Server response: 46 ms
46 msYour server sent the HTML in 46 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 18.5 s
18.5 sVisually, the page fills in at 18.5 s (Speed Index). Good is under 3.4 s.
80 images without width and height
80 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (9.4 s).
Time to Interactive: 4.9 s
4.9 sThe page becomes fully interactive after 4.9 s. Good is under 3.8 s.
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
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 51 ms
51 msScripts block the page for only 51 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 49.8 MB in 104 requests
49.8 MBYour homepage downloads 49.8 MB in 104 requests on a phone: images 49.2 MB (84), scripts 408 KiB (12) and fonts 101 KiB (4). Under 2 MB keeps phones on slow connections fast.
10 images over 500 KB
10 images weigh 42.9 MB together. On a phone connection a single image that size takes seconds.
10 images far larger than shown
40.1 MB10 images are downloaded at several times the size a phone draws them, for example 2022-10_25_Birds-E-SQUARE-CROP.jpg at 4,320 px wide, shown at 370 px. Resized copies would save about 40.1 MB.
32 images below the first screen load straight away
32 images further down the page (43.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
25 images in older formats
25 images (43.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.
About 14.1 g of CO₂ per visit
14.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 14.12 g of CO₂e: 1694.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
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.
49 links without text
49 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 166 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 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “NAK Design Strategies - Urban Design and Landscape Architecture Firm”.
82 H1 headlines
There are 82 <h1> headlines (“The Conservancy”, “Bayview Hill Community Park” and “Flemingdon Park”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
272 internal links, 3 external
The homepage links to 272 pages on nakdesignstrategies.com and 3 external pages.
5 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “NAK Design Strategies is a top urban design and landscape architecture firm with offices across North America in Toront…”.
Canonical URL set
The canonical URL is https://www.nakdesignstrategies.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.nakdesignstrategies.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.nakdesignstrategies.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,012 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages hidden from search
https://www.nakdesignstrategies.com/regions/alberta, https://www.nakdesignstrategies.com/regions/ontario and https://www.nakdesignstrategies.com/regions/usa are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages without a meta description
https://www.nakdesignstrategies.com/service, https://www.nakdesignstrategies.com/regions/alberta, https://www.nakdesignstrategies.com/regions/ontario, https://www.nakdesignstrategies.com/regions/usa, https://www.nakdesignstrategies.com/projects/the-conservancy and https://www.nakdesignstrategies.com/projects/bayview-hill-community-park have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
https://www.nakdesignstrategies.com/leadership and https://www.nakdesignstrategies.com/services/urban-design 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.
13 pages slow to respond
https://www.nakdesignstrategies.com/projects, https://www.nakdesignstrategies.com/news, https://www.nakdesignstrategies.com/ideas, https://www.nakdesignstrategies.com/careers, https://www.nakdesignstrategies.com/leadership and https://www.nakdesignstrategies.com/contact and 7 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 96 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 392 words of copy
The homepage carries about 392 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 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 nakdesignstrategies.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2020.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on nakdesignstrategies.com, including 10 speed issues, 3 SEO issues and 6 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.