Website review, no card needed
swing.dev website review
Visit site (opens in a new tab)Reviewed 23 October 202614 issues · 61 checks
This review found 14 issues worth fixing on swing.dev, 2 of them high impact, across 61 checks. The most urgent: 2 text elements with low contrast. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.2 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
Speed
Reduce unused JavaScript
150 ms · 26 KiBAbout 26 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
100 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 81 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.
Duplicated JavaScript
4 KiB4 KiB JavaScript is shipped twice across bundles.
Use efficient cache lifetimes
1 KiB2 files are served with short cache lifetimes, so returning visitors download them again (1 KiB).
3 checks passed
Mobile performance score: 93
93/100Your mobile performance score is 93 (desktop: 100). That is in Google's “good” band (90 and up).
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 494 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Arrow down to next section”.
Time to Interactive: 4.1 s
4.1 sThe page becomes fully interactive after 4.1 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.
5 checks passed
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 3.3 s
3.3 sVisually, the page fills in at 3.3 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).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 16 ms
16 msScripts block the page for only 16 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
41 KiB1 image is downloaded at several times the size a phone draws it, for example image at 558 px wide, shown at 111 px. Resized copies would save about 41 KiB.
4 images below the first screen load straight away
4 images further down the page (177 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.29 g of CO₂e: 34.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.0 MB in 29 requests
1.0 MBYour homepage downloads 1.0 MB in 29 requests on a phone: images 692 KiB (9), scripts 236 KiB (12) and fonts 56 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
39 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: 39 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
16 internal links, 7 external
The homepage links to 16 pages on swing.dev and 7 external pages.
6 checks passed
Meta description: 131 characters
Your meta description is 131 characters: “Top-notch developers, designers and business leaders modernizing home insurance industry. We do the software the best p…”.
One H1 headline
Your main headline reads: “Swing intoaction”.
Title: 57 characters
Your title is a healthy 57 characters: “SwingDev – a hippo company | Developed with a human touch”.
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://swing.dev/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://www.swing.dev/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 (311 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://www.swing.dev/about, https://www.swing.dev/culture, https://www.swing.dev/careers, https://www.swing.dev/work, https://www.swing.dev/pets and https://www.swing.dev/careers/open-positions and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.swing.dev/careers/open-positions has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.swing.dev/careers/open-positions and https://www.swing.dev/privacy-policy 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.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 8 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 8 pages that loaded have a <title>.
Best practices
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 282 words of copy
The homepage carries about 282 words of visible text.
1 checks passed
1 call to action
The homepage has 1 call to action, for example “Join us!See open positions”.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 swing.dev, 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 © 2025.
Stack
- Framework
- Next.js
- Hosting
- Heroku
Hiring
- Hiring
- 8 open roles
- Teams
- People (3), Back-end (2), Design (1), General (1)
- Job board
- lever
- Careers page
- www.swing.dev/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on swing.dev, including 2 speed issues, 2 SEO issues and 4 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.