Website review, no card needed
projectdata.io website review
Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 77 checks
This review found 33 issues worth fixing on projectdata.io, 10 of them high impact, across 77 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
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
2.2 s · 443 KiBAbout 443 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Squarespace, sibforms.com and Clarity and others), adding 1.9 MB and 712 ms of main-thread time.
Use efficient cache lifetimes
650 ms · 170 KiB7 files are served with short cache lifetimes, so returning visitors download them again (170 KiB).
Improve image delivery
400 ms · 227 KiB7 images could be 227 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Squarespace adds 526 ms
526 msSquarespace costs a phone 526 ms of main-thread work and 952 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.
Reduce unused CSS
450 ms · 125 KiBAbout 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
1,911 HTML elements
The page has 1,911 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
squarespace-cdn.com adds 0 ms
0 mssquarespace-cdn.com costs a phone 0 ms of main-thread work and 552 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.
Legacy JavaScript
150 ms · 107 KiBPolyfills for old browsers add 107 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 227 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 841 ms of it running JavaScript. That is comfortably low.
Server response: 90 ms
90 msYour server sent the HTML in 90 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 218 ms
218 msScripts block taps and scrolling for 218 ms in total while the page loads. Good is under 200 ms.
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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.0 MB in 89 requests
2.0 MBYour homepage downloads 2.0 MB in 89 requests on a phone: scripts 1.0 MB (44), images 476 KiB (13) and fonts 195 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.4 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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 20 images in the HTML carry an alt attribute.
46 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: 46 passed and 3 failed. 3 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.
Structured data has 2 problems
Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/67cf2c73f4307f611c7…”.
67 internal links, 8 external
The homepage links to 67 pages on projectdata.io and 8 external pages.
6 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “Streamline project efficiency with Project Data Suite. Sync, backup, and migrate to Microsoft's enhanced tools effortle…”.
Title: 41 characters
Your title is a healthy 41 characters: “Project Data | Enhance Project Management”.
Canonical URL set
The canonical URL is https://projectdata.io/.
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://projectdata.io/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://projectdata.io/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 (1,266 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://projectdata.io/configurationmigration and https://projectdata.io/partners all use the title “Project Online Configuration Migration to Planner — Project Data”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://projectdata.io/sync-to-dataverse, https://projectdata.io/pricing and https://projectdata.io/project-ai have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://projectdata.io/configurationmigration and https://projectdata.io/partners use the same meta description. A description written for each page earns more clicks.
13 pages without an H1
https://projectdata.io/migration, https://projectdata.io/backups, https://projectdata.io/copy, https://projectdata.io/provision, https://projectdata.io/integration-scenarios and https://projectdata.io/configurationmigration and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
4 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355046232&tm=sqsp_ui&Ver=2&mid=5f430e1e-2296-4384-8f4a-374ad01f031d&bo=1&sid=1472b5e0dce511f1acb0439a4f19f7e6&vid=1472b340dce511f1b220d97bd4a1b8b2&vids=1&msclkid=N&pi=.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/67cf2c73f4307f611c7048f7/115/5c5…”.
2 checks passed
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 11-field form
Your longest form asks for 11 fields (4 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 607 words of copy
The homepage carries about 607 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: “See plans and pricing”.
7 calls to action
The homepage has 7 calls to action, for example “Pricing”, “Contact Us” and “See plans and pricing”.
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
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Microsoft Ads and Microsoft Clarity (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies, 1 of them by other companies (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.
16 other companies contacted
Loading the homepage contacts 16 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 projectdata.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Squarespace
- Hosting
- Squarespace
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on projectdata.io, including 17 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.