Website review, no card needed
fischsolutions.com website review
Visit site (opens in a new tab)Reviewed 5 November 202645 issues · 90 checks
This review found 45 issues worth fixing on fischsolutions.com, 21 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
67DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.7 s
2.5 s
3.3 s
4.1 s
5.0 s
5.8 s
6.6 s
Speed
Use efficient cache lifetimes
5.8 s · 4.3 MB210 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).
Render-blocking requests
3.5 s48 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
5,628 HTML elements
The page has 5,628 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 1.4 MBAbout 1.4 MB 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 (YouTube, Google Tag Manager and pipedriveassets.com and others), adding 2.7 MB and 1.4 s of main-thread time.
Improve image delivery
500 ms · 741 KiB6 images could be 741 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
YouTube adds 871 ms
871 msYouTube costs a phone 871 ms of main-thread work and 2.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.
Reduce unused CSS
740 ms · 243 KiBAbout 243 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 350 ms. During a long task the page ignores taps.
Google Tag Manager adds 276 ms
276 msGoogle Tag Manager costs a phone 276 ms of main-thread work and 314 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.
Minify CSS
140 ms · 9 KiB9 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 30 ms
30 msYour server sent the HTML in 30 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.0 s
15.0 sYour largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE HUDSON VALLEY'S MOST TRUSTED IT & CYBERSECURITY PARTNER…”.
Time to Interactive: 35.6 s
35.6 sThe page becomes fully interactive after 35.6 s. Good is under 3.8 s.
Speed Index: 10.1 s
10.1 sVisually, the page fills in at 10.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images 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.036
0.036The layout barely moves while loading (CLS 0.036, good is under 0.1).
Images and page weight
Page weight: 7.6 MB in 277 requests
7.6 MBYour homepage downloads 7.6 MB in 277 requests on a phone: images 3.9 MB (111), scripts 2.7 MB (72) and stylesheets 403 KiB (57). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
vignette_2_firewall_ai-768x768.png weighs 758 KiB. On a phone connection a single image that size takes seconds.
23 images below the first screen load straight away
23 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
11 images in older formats
11 images (826 KiB) 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.
3 images far larger than shown
377 KiB3 images are downloaded at several times the size a phone draws them, for example vignette_2_firewall_ai-768x768.png at 390 px wide, shown at 104 px. Resized copies would save about 377 KiB.
About 2.1 g of CO₂ per visit
2.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 257.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
38 tap targets too small
38 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (17 elements)
Elements must only use permitted ARIA attributes: 17 elements on the page fail this check, rated serious by axe-core.
Links look like plain text
8 links inside paragraphs rely on colour alone to stand out.
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.
Orphan list items
Some list items are not inside a list.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
27 links without text
27 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 154 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 11 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (90 characters)
Your title is 90 characters, so Google will cut it off around 60: “Managed IT Services | Cybersecurity AI & VOIP Phones | Hudson Valley, NY - Fisch Solutions”.
Meta description is long (184 characters)
Your meta description is 184 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://fischsolutions.com/sitemap.xml, so Google discovers your pages only by following links.
12 links crawlers can't follow
12 links have no real href, so search engines can't follow them.
10 links with vague text
10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
185 internal links, 232 external
The homepage links to 185 pages on fischsolutions.com and 232 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Hudson Valley Managed IT, Cybersecurity, AI & VoIP Phone Systems — Serving NY, NJ & CT”.
Canonical URL set
The canonical URL is https://fischsolutions.com/.
Structured data in place
Structured data found: Article, FAQPage, ImageObject, Organization and Person.
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.
AI search readiness
No llms.txt
There is no https://fischsolutions.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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (5,638 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without an H1
https://fischsolutions.com/ai-services, https://fischsolutions.com/solutions/it-outsource, https://fischsolutions.com/solutions/structured-wiring, https://fischsolutions.com/solutions/cloud-iot-solutions and https://fischsolutions.com/solutions/hudson-valley-business-phone-systems 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 62 found) and read each the way a search engine does.
6 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.
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
7 broken images
7 images failed to load on a phone, for example https://lh5.googleusercontent.com/-9Yx6QcvzuEY/AAAAAAAAAAI/AAAAAAAAAAA/AMZuucmuhvCoJ4awUEnZ9mczt8imORkzpg/s128-c0x00000000-cc-rp-mo-ba3/photo.jpg.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 small tap targets
3 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 4,324 words of copy
The homepage carries about 4,324 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “Book A 15-Minute Discovery Call >”.
14 calls to action
The homepage has 14 calls to action, for example “Contact Us”, “Book A 15-Minute Discovery Call >” and “Ready To Talk Now? Contact Us >”.
4 short forms
4 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 131 testimonial or review blocks, 3 customer or partner logos, 5 trust badges and “Trusted by 100+ Clients”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 7 phone links and 20 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
31 other companies contacted
Loading the homepage contacts 31 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 fischsolutions.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 Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on fischsolutions.com, including 18 speed issues, 5 SEO 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.