Website review, no card needed
3sharp.com website review
Visit site (opens in a new tab)Reviewed 19 October 202630 issues · 96 checks
This review found 30 issues worth fixing on 3sharp.com, 12 of them high impact, across 96 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
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.7 s
3sharp.com does not allow embedding, so this is Google's rendering of the page.
Speed
Use efficient cache lifetimes
3.8 s · 629 KiB8 files are served with short cache lifetimes, so returning visitors download them again (629 KiB).
Render-blocking requests
1.9 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Reduce unused CSS
1.4 s · 179 KiBAbout 179 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused JavaScript
1.0 s · 283 KiBAbout 283 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59 (desktop: 93). Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
600 ms · 94 KiBPolyfills for old browsers add 94 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 600 ms faster on a phone.
Azure Web Services adds 88 ms
88 msAzure Web Services costs a phone 88 ms of main-thread work and 628 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.
4 third-party services on the page
4 third-party services load with your homepage (Azure Web Services, Shopify and Google Fonts and others), adding 718 KiB and 110 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.
Improve image delivery
13 KiB2 images could be 13 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 93 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 285 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are Storytellers”.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
17 images without width and height
17 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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.8 MB in 172 requests
1.8 MBYour homepage downloads 1.8 MB in 172 requests on a phone: other files 784 KiB (105), scripts 597 KiB (34) and images 240 KiB (25). That is a lean page.
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
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3 and h1 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (6 characters)
Your title is only 6 characters: “3Sharp”. Between 30 and 65 characters leaves room to say what you do and for whom.
9 H1 headlines
There are 9 <h1> headlines (“We are Storytellers”, “We are Technologists” and “We are Product Marketers”). One clear main headline is easier for people and search engines.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), 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.
14 internal links, 11 external
The homepage links to 14 pages on 3sharp.com and 11 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://3sharp.com/.
Structured data in place
Structured data found: Organization and WebSite.
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://3sharp.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, 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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (362 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
/pages/contact-us and /policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
/pages/contact-us and /pages/microsoft-teams 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.
6 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.
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 8 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'ready')”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
20 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 91 days; one year is the recommended minimum.
2 links through redirect chains
2 links go through two or more redirects, for example https://www.microsoft.com/en-us/education/interactive-demos.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
7 checks passed
Served over HTTPS
The homepage is served over HTTPS (3sharp.com).
Valid certificate (72 days left)
The certificate from Let's Encrypt · YE1 verifies for 3sharp.com and is valid for another 72 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://3sharp.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
All 16 links work
All 16 links checked from your homepage (9 internal, 7 external) answered without errors.
Domain and trust
Domain expires in 81 days
3sharp.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.
No CAA record
3sharp.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
3sharp.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
1 checks passed
Domain is 24 years old
24 years3sharp.com was registered in Jan 2002 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Content and conversion
Thin social proof
Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 341 words of copy
The homepage carries about 341 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: “Contact Us”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Talk to Us” and “Experience the EDU DEMO”.
1 short form
A short form (7 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: HubSpot.
Email authentication
Email authentication score: 90/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: quarantine
DMARC tells receivers to quarantine mail that fails authentication.
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:9013784.spf01.hubspotemail.net include:authsmtp.com -all”.
DKIM signing found
A DKIM key is published (selector “selector2”, “s1” and “s2”), so receivers can verify mail really came from you.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This free review found 30 issues on 3sharp.com, including 12 speed issues, 4 SEO issues and 2 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.