Website review, no card needed

swyftfilings.com logo

swyftfilings.com website review

Visit site (opens in a new tab)Reviewed 22 October 202627 issues · 79 checks

This review found 27 issues worth fixing on swyftfilings.com, 10 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s3.0 sMay 2Oct 173.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.4 s
Jun 6, 20263.3 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.6 s
Oct 17, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
245 ms200 msMay 2Oct 17229 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026205 ms
May 9, 2026213 ms
May 16, 2026232 ms
May 23, 2026237 ms
May 30, 2026240 ms
Jun 6, 2026239 ms
Jun 13, 2026230 ms
Jun 20, 2026236 ms
Jun 27, 2026228 ms
Jul 4, 2026233 ms
Jul 11, 2026235 ms
Jul 18, 2026229 ms
Jul 25, 2026237 ms
Aug 1, 2026237 ms
Aug 8, 2026231 ms
Aug 15, 2026236 ms
Aug 22, 2026234 ms
Aug 29, 2026226 ms
Sep 5, 2026236 ms
Sep 12, 2026232 ms
Sep 19, 2026233 ms
Sep 26, 2026228 ms
Oct 3, 2026226 ms
Oct 10, 2026228 ms
Oct 17, 2026229 ms

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

Full-page screenshot of swyftfilings.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. swyftfilings.com at 0.4 s0.4 s
  2. swyftfilings.com at 0.8 s0.8 s
  3. swyftfilings.com at 1.1 s1.1 s
  4. swyftfilings.com at 1.5 s1.5 s
  5. swyftfilings.com at 1.9 s1.9 s
  6. swyftfilings.com at 2.3 s2.3 s
  7. swyftfilings.com at 2.6 s2.6 s
  8. swyftfilings.com at 3.0 s3.0 s

Speed

10 to fix57
  • Use efficient cache lifetimes

    2.6 s · 8.2 MB

    34 files are served with short cache lifetimes, so returning visitors download them again (8.2 MB).

  • 3,193 HTML elements

    The page has 3,193 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    150 ms · 1.8 MB

    7 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    900 ms · 723 KiB

    About 723 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and niceincontact.com and others), adding 2.6 MB and 905 ms of main-thread time.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 48). Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 704 ms

    704 ms

    Google Tag Manager costs a phone 704 ms of main-thread work and 910 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.

  • Render-blocking requests

    450 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 360legal.com adds 0 ms

    0 ms

    360legal.com costs a phone 0 ms of main-thread work and 1.2 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.

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

1 checks passed
  • Server response: 41 ms

    41 ms

    Your server sent the HTML in 41 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 25.1 s

    25.1 s

    Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 40.1 s

    40.1 s

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

  • Speed Index: 12.4 s

    12.4 s

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

  • Total Blocking Time: 359 ms

    359 ms

    Scripts block taps and scrolling for 359 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 205 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 12% slower for real visitors

    +12%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 767 ms

    767 ms

    Real visitors wait 767 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.012

    0.012

    The layout barely moves while loading (CLS 0.012, good is under 0.1).

Images and page weight

6 to fix19
  • Page weight: 10.8 MB in 81 requests

    10.8 MB

    Your homepage downloads 10.8 MB in 81 requests on a phone: images 8.7 MB (19), scripts 1.9 MB (27) and HTML 78 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 8.5 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    6.8 MB

    3 images are downloaded at several times the size a phone draws them, for example business-hero.png at 2,368 px wide, shown at 342 px. Resized copies would save about 6.8 MB.

  • 5 images in older formats

    5 images (8.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 (6.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    background.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 3.0 g of CO₂ per visit

    3.05 g

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

Accessibility

4 to fixGoogle 9293
  • 36 text elements with low contrast

    36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 203 internal links, 25 external

    The homepage links to 203 pages on swyftfilings.com and 25 external pages.

8 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Start your LLC, corporation, nonprofit, or DBA. Basic starts with a $0 service fee. State filing fees apply. Form your …”.

  • One H1 headline

    Your main headline reads: “The Confident Way to Form Your Business Online”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Online LLC & Corporation Formation Services | Swyft Filings”.

  • Canonical URL set

    The canonical URL is https://www.swyftfilings.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://www.swyftfilings.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,151 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.swyftfilings.com/llms.txt (40 KiB, 361 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 121 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No form on the homepage

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

  • About 2,551 words of copy

    The homepage carries about 2,551 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call (877) 777-0450” and “Get Started”.

  • 30 calls to action

    The homepage has 30 calls to action, for example “Call (877) 777-0450”, “Start a Business” and “Get Started”.

  • Social proof on the page

    Social proof on the homepage: 15 testimonial or review blocks, 7 customer or partner logos, a star rating, 1 trust badge and “600,000+ Businesses”.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 4 mores (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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 37 other companies contacted

    Loading the homepage contacts 37 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 swyftfilings.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Netlify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on swyftfilings.com, including 14 speed issues and 1 conversion gap. 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25