https://www.roundskysolutions.com·Oct 7, 2026, 01:34 PM UTC·12 technologies·AI

www.roundskysolutions.com

Built with Custom Css, Custom Error Page, Google Fonts, Html5, Inline Svg and 7 more

https://www.roundskysolutions.com

Performance

TTFB

716ms

DOM Ready

729ms

Load Complete

927ms

Requests

Total Size

1KB

Domains

Errors

Technologies

Other

Custom Css

AIhigh

Custom Error Page

AIhigh

Google Fonts

AIhigh

Html5

Scripthigh

Inline Svg

AIhigh

Inter Font

Scripthigh

Open Sans

AIhigh

Roboto

AIhigh

Bem Naming

AImedium

Adobe Illustrator

AIlow

Http Server

AIlow

Waf

AIlow

Company estimate

Company

—

Estimated annual tech spend

$5K

The page only returns a generic 403 Forbidden error page (custom theme with inline SVG clouds) and contains no company name, logo, product, or any identifying content. The company could not be identified from page content, so no valuation or other company attributes were inferred; tech spend reflects a clearly minimal static/small operation.

SEO recommendations

SEO health score

The homepage is serving a 403 Forbidden page carrying a noindex directive, which removes the entire site from search engines; restoring a proper 200 response with real content is the only fix that matters before any other optimization.

Improve page titlesVery High
The only title is the generic error string '403 - Forbidden' with zero keyword relevance, and the noindex directive ensures it can never rank.
→ Fix the server/security rule returning 403 on the root path and restore a keyword-rich homepage title for Round Sky Solutions.
95%
impact
Add structured data to your websiteVery High
No JSON-LD or schema.org markup exists anywhere in the document, so Google receives no entity signals about the business.
→ Once the real homepage is served, add Organization/WebSite JSON-LD with name, url, logo, and contact details.
90%
impact
Optimize your sitemapVery High
No XML sitemap link or robots reference appears in the HTML (or any served asset), so crawl discovery is entirely dependent on external links.
→ Generate an XML sitemap, reference it in robots.txt, and submit it in Search Console once the server returns 200s.
90%
impact
Improve internal linkingVery High
The page contains zero internal links, so crawlers have no path to deeper pages and no site hierarchy exists.
→ Serve a real homepage with a navigation header linking to core service pages using descriptive keyword anchors.
85%
impact
Review similar contentHigh
The document is a bare 403 error page with no real content — an extreme case of thin content that must never be indexed.
→ Replace it with the actual homepage copy and ensure it is unique rather than a duplicate of another site section.
85%
impact
Trailing slashes may cause duplicate contentHigh
No rel=canonical tag is present, so trailing-slash versus non-trailing-slash variants of the URL are not canonicalized.
→ Serve a self-referencing canonical tag and enforce a single URL form with 301s once the site is operational.
80%
impact
Content to-do listMedium
There is no semantic content: only a CSS-styled error heading, no H1 hierarchy, body copy, or topical coverage of the business.
→ Rebuild the page with a proper H1, descriptive intro, and sections covering Round Sky Solutions' services and differentiators.
70%
impact
Improve page speedHigh
The page loads render-blocking Google Fonts CSS and a large inline SVG error graphic, though speed is moot while the server returns an error page.
→ Resolve the 403 first, then self-host or preload fonts and inline critical CSS on the restored homepage.
65%
impact
Improve meta descriptionsMedium
The document has no meta description at all, so search snippets would be blank or auto-generated with no CTR appeal.
→ Write a 150-160 character description for the restored homepage that includes the primary keyword and a call to action.
60%
impact
Avoid internal redirectsMedium
No redirect headers are visible in the HTML, but with the site erroring at 403 the presence of misrouted redirect chains cannot be verified.
→ After restoring the server, crawl the site to confirm every URL resolves with a single 200 or a one-hop 301.
40%
impact
Add OpenGraph tagsLow
No og: or twitter: meta tags are present, so links shared to social platforms render without title, image, or description.
→ Add og:title, og:description, og:image, and og:url tags to the restored homepage.
25%
impact

AI-generated SEO assessment · impact = estimated priority for this page

Specification compliance (30 shortcomings)

Specification compliance score

17/27 required and 6/30 recommended practices implemented. 30 shortcomings to address.

17/27

Required

6/30

Recommended

Shortcomings

51%

Overall

The HTML doctypeRequired
Standards-mode <!doctype html> present.
100%
Implemented
The lang attribute on <html>Required
<html> declares a language.
100%
Implemented
<meta charset>Required
Character encoding declared.
100%
Implemented
<meta viewport>Required
Responsive viewport meta present.
100%
Implemented
The <title> elementRequired
Page has a non-empty <title>.
100%
Implemented
<meta name="description">Recommended
No meta description — search engines may show a poor snippet.
0%
Not implemented
Canonical URL (rel="canonical")Recommended
No rel="canonical" — risks duplicate-content dilution.
0%
Not implemented
Favicons and app iconsRecommended
No favicon/app-icon links found.
0%
Not implemented
<meta name="theme-color">Recommended
No theme-color — mobile browser UI will not match your brand.
0%
Not implemented
<meta name="color-scheme">Recommended
No color-scheme — form controls and scrollbars will not adapt to dark mode.
0%
Not implemented
Open Graph protocolRecommended
No Open Graph tags — shared links will render without rich previews.
0%
Not implemented
Feed discovery with rel="alternate"Recommended
No feed discovery link found — only relevant if the site publishes a feed.
—
Needs review
Feed content hygieneRecommended
Feed content quality cannot be assessed from a page scan.
—
Needs review
Popover APIRecommended
No popover attributes — only applies if the page has popovers/menus.
—
Needs review

robots.txtRecommended
No robots.txt found at the site root.
0%
Not implemented
XML sitemapsRecommended
No sitemap.xml found and none referenced in robots.txt.
0%
Not implemented
Sitemap index filesRecommended
No sitemap index — only needed once you exceed 50k URLs / 50MB.
—
Needs review
Image and video sitemap extensionsOptional
No image/video sitemap extensions detected.
—
Needs review
URL structureRecommended
URL path is clean and readable.
100%
Implemented
Redirects (301/302/308)Required
http:// returned 403 — verify it redirects to the canonical https URL.
50%
Partial
Soft 404sAvoid
Nonexistent path returned 403; ensure missing pages return 404.
50%
Partial
Meta robots and X-Robots-TagRequired
This page is set to noindex — search engines will not index it. Remove it unless intentional.
0%
Not implemented
Heading hierarchyRequired
Exactly one <h1> heading.
100%
Implemented
Internal linkingRecommended
Few internal links found — add contextual links between related pages.
40%
Partial
Structured data (JSON-LD)Recommended
No JSON-LD — add schema.org structured data for rich results.
0%
Not implemented
BreadcrumbsRecommended
No breadcrumb structured data or navigation found.
0%
Not implemented
IndexNowOptional
IndexNow integration cannot be detected from a page scan.
—
Needs review

Colour contrastRequired
Colour contrast requires rendering analysis — review with an automated contrast checker.
—
Needs review
Image alt textRequired
No <img> elements to caption.
100%
Implemented
Form labelsRequired
No form fields requiring labels.
100%
Implemented
Keyboard navigationRequired
Keyboard operability needs interactive testing.
—
Needs review
Visible focus indicatorsRequired
Focus-indicator visibility needs rendering review.
—
Needs review
Skip linksRecommended
No skip link — keyboard users must tab through the nav on every page.
0%
Not implemented
Semantic HTML and landmarksRequired
No semantic landmark elements — the page is built from generic <div>s.
0%
Not implemented
ARIA — first rule of ARIARecommended
No obvious ARIA misuse, but full review needs assistive-tech testing.
—
Needs review
Descriptive link textRequired
Link-text quality needs manual review.
—
Needs review
Empty links and buttonsAvoid
No empty links or buttons detected.
100%
Implemented
Accessible form errorsRequired
Form-error accessibility needs interactive testing.
—
Needs review
Document and parts languageRequired
Document language is declared.
100%
Implemented
Reduced motionRequired
No inline prefers-reduced-motion rule — verify external CSS respects reduced motion.
—
Needs review
Accessibility overlaysAvoid
No accessibility-overlay widget detected.
100%
Implemented
Captions and transcriptsRequired
No audio/video requiring captions.
100%
Implemented
Accessible data tablesRequired
No data tables on the page.
100%
Implemented
Touch target sizeRequired
Touch-target sizing needs rendering measurement.
—
Needs review
Hidden until foundRecommended
Not used — only relevant for collapsible/accordion content.
—
Needs review
Native interactive elementsRecommended
Could not confirm use of native interactive elements.
—
Needs review
CSS state and relational selectorsRecommended
CSS selector strategy needs source review.
—
Needs review

HTTPS and TLSRequired
Page is served over HTTPS.
100%
Implemented
HSTS (Strict-Transport-Security)Required
No Strict-Transport-Security header — browsers will not enforce HTTPS.
0%
Not implemented
Content Security Policy (CSP)Recommended
No CSP header — the page has no defence-in-depth against injected scripts.
0%
Not implemented
/.well-known/security.txtRecommended
No /.well-known/security.txt — researchers have no disclosure contact.
0%
Not implemented
X-Content-Type-Options: nosniffRequired
No X-Content-Type-Options: nosniff — browsers may MIME-sniff responses.
0%
Not implemented
Clickjacking protectionRequired
No frame-ancestors or X-Frame-Options — the page can be framed for clickjacking.
0%
Not implemented
Referrer-PolicyRecommended
No Referrer-Policy — full URLs may leak to third parties.
0%
Not implemented
Permissions-PolicyRecommended
No Permissions-Policy — powerful browser features are not locked down.
0%
Not implemented
Subresource Integrity (SRI)Recommended
No cross-origin scripts requiring SRI.
100%
Implemented
Cookie attributes — Secure, HttpOnly, SameSiteRequired
No cookies set on the document response.
100%
Implemented
DNS CAA recordsRecommended
CAA records are not collected by the scanner — check your DNS provider.
—
Needs review
DNSSECOptional
DNSSEC status is not collected by the scanner.
—
Needs review

Well-known URIsRecommended
No /.well-known/ resources found.
0%
Not implemented
/.well-known/change-passwordOptional
No change-password redirect — recommended if the site has accounts.
—
Needs review
/.well-known/openid-configurationOptional
Not present — only relevant for OIDC identity providers.
—
Needs review
/.well-known/api-catalogRecommended
Not present — recommended if the site exposes public APIs.
—
Needs review
/.well-known/webfingerOptional
Not present — only relevant for federated identity.
—
Needs review
/.well-known/apple-app-site-associationOptional
Not present — only needed for iOS Universal Links.
—
Needs review
/.well-known/assetlinks.jsonOptional
Not present — only needed for Android App Links.
—
Needs review
/.well-known/nodeinfoOptional
Not present — only relevant for Fediverse servers.
—
Needs review
/.well-known/traffic-adviceOptional
Not present — optional prefetch-proxy control file.
—
Needs review

Agent readinessRecommended
No agent-readiness signals (no llms.txt, no structured data).
0%
Not implemented
/llms.txtRecommended
No /llms.txt — agents have no curated map of your key content.
0%
Not implemented
/llms-full.txtOptional
No /llms-full.txt — optional full-content variant.
—
Needs review
Per-page Markdown source endpointsRecommended
No Markdown source endpoint detected — recommended for content/doc sites.
—
Needs review
robots.txt for AI crawlersRecommended
robots.txt has no explicit AI-crawler rules — state your stance on GPTBot/ClaudeBot/etc.
0%
Not implemented
Content Signals in robots.txtOptional
No Content-Signal directives — optional usage-preference signalling.
—
Needs review
Web Bot Auth — verifiable bot identityOptional
Web Bot Auth support cannot be detected from a scan.
—
Needs review
Stable URLsRequired
URL has no obvious session/volatile parameters.
100%
Implemented
Structured data for agentsRecommended
No structured data — agents must scrape prose instead of reading typed facts.
0%
Not implemented
Machine-readable formatsRecommended
No machine-readable alternates detected — recommended for listings/data pages.
—
Needs review
HTTP Link headers for discoveryRecommended
No HTTP Link header — recommended to surface related resources to agents.
—
Needs review
MCP and tool discoveryOptional
No MCP/tool discovery endpoint — optional.
—
Needs review
A2A agent cardsOptional
No A2A agent card — optional.
—
Needs review
Agent Skills discoveryRecommended
Agent Skills discovery cannot be detected automatically.
—
Needs review
DNS for AI Discovery (DNS-AID)Optional
DNS-AID records are not collected by the scanner.
—
Needs review
NLWeb — conversational interface discoveryOptional
NLWeb support cannot be detected automatically.
—
Needs review
WebMCP — browser-native tools for agentsOptional
WebMCP support cannot be detected automatically.
—
Needs review
Schemamap — discoverable JSON-LD endpointsOptional
Schemamap support cannot be detected automatically.
—
Needs review

Core Web Vitals (LCP, INP, CLS)Required
Lab load completed in 927ms (a proxy). Confirm LCP/INP/CLS with field data.
85%
Partial
Image optimisationRequired
No raster images, or none captured.
100%
Implemented
Lazy loading images, iframes, and videoRecommended
Too few images to need lazy-loading.
100%
Implemented
Preload, prefetch, preconnectRecommended
No resource hints — preconnect to critical origins and preload the LCP asset.
0%
Not implemented
Cache-Control headersRequired
No Cache-Control header on the document — set explicit caching for HTML and assets.
0%
Not implemented
No-Vary-Search response headerRecommended
Not set — optional; helps cache/prefetch URLs that differ only by tracking params.
—
Needs review
Compression (gzip, brotli, zstd)Required
Document is compressed (br).
100%
Implemented
Web font loadingRecommended
No inline font-display/preload — ensure web fonts use font-display: swap to avoid invisible text.
—
Needs review
Critical CSS and render-blocking resourcesRecommended
1 render-blocking stylesheet(s) in <head>.
100%
Implemented
Script loading — defer, async, moduleRecommended
No external blocking scripts.
100%
Implemented
HTTP/2 and HTTP/3Recommended
Protocol version not captured — verify HTTP/2/3 is enabled at your edge/CDN.
—
Needs review
Speculation RulesRecommended
No Speculation Rules — optionally prerender/prefetch likely next pages.
—
Needs review
Resource hints overviewRecommended
No resource hints found on the page.
0%
Not implemented
View TransitionsRecommended
No View Transitions detected — optional polish for navigations.
—
Needs review
Back/forward cache (BFCache)Recommended
BFCache eligibility needs runtime testing.
—
Needs review
Visibility-aware renderingRecommended
No content-visibility detected — optional offscreen-render optimisation.
—
Needs review
CSS containmentOptional
No CSS containment detected — optional.
—
Needs review
Scroll-driven animationsOptional
Not detected — optional.
—
Needs review
Scrollbar gutterRecommended
No scrollbar-gutter — optional; prevents layout shift when scrollbars toggle.
—
Needs review

Privacy policyRequired
No privacy policy link found — link one from every page (usually the footer).
0%
Not implemented
Cookie consentRequired
No consent manager detected (and no document cookies) — required if you set non-essential cookies.
—
Needs review
Global Privacy Control (GPC)Recommended
GPC handling is server-side and cannot be confirmed from a scan.
—
Needs review
Third-party scripts and privacyRecommended
No third-party scripts detected.
100%
Implemented
Privacy-respecting analyticsRecommended
No analytics detected, or an unrecognised provider.
—
Needs review
Data minimisationRecommended
Data-minimisation practices need a manual review of forms and backend.
—
Needs review

Custom error pages (404, 500)Required
Missing path returned 403 — ensure it is a 404 with a custom page.
50%
Partial
Maintenance pages and 503Recommended
Maintenance behaviour can only be observed during downtime.
—
Needs review
Offline support and service workersOptional
No service worker detected — optional offline/PWA support.
—
Needs review
Web app manifestRecommended
No <link rel="manifest"> — add a web app manifest for installability.
0%
Not implemented
Monitoring and uptimeRecommended
Monitoring is operational and cannot be detected from the page.
—
Needs review

Deterministic audit against the website specification checklist. “Needs review” items can't be confirmed from a headless scan and are excluded from the score.

DNS & Infrastructure

DNSSiteGround

EmailGoogle Workspace

HostingGoogle Cloud

IP Addresses

34.174.91.22

Google Cloud (us-south1)

🇺🇸Dallas, United States

Nameservers

ns1.siteground.net

ns2.siteground.net

Mail Servers (MX)

1aspmx.l.google.com

5alt2.aspmx.l.google.com

5alt1.aspmx.l.google.com

10alt3.aspmx.l.google.com

10alt4.aspmx.l.google.com

AI Analysis Notes

·DNS hosted on SiteGround (ns1.siteground.net, ns2.siteground.net)
·Email handled by Google Workspace (aspmx.l.google.com and alternates)
·Origin server runs on Google Cloud (us-south1), AS396982 Google LLC, IP 34.174.91.22
·SPF record uses +ip4:34.174.196.85 and includes DNSSmarthost (roundskysolutions.com.spf.auto.dnssmarthost.net), suggesting DNSSmarthost-based email delivery in addition to Google
·google-site-verification TXT record confirms Google Workspace / Search Console setup
·facebook-domain-verification TXT record present for Facebook/Meta domain verification

Email & Deliverability

Email health score

Google Workspace

roundskysolutions.com runs on Google Workspace (Google MX + gsmtp banner) with valid MX, SPF, and DKIM, so mail is received and basic authentication passes — but DMARC is still at p=none and SPF only uses ~all, so the domain remains spoofable. Enforce DMARC and harden SPF, then add MTA-STS/TLS-RPT.

Mail configuration

Mail servers (MX)aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com
5 MX records — the domain can receive mail.
SPFv=spf1 +a +mx +ip4:34.174.196.85 include:roundskysolutions.com.spf.auto.dnssmarthost.net ~all
SPF present but uses a soft fail (~all) — consider tightening to -all once you confirm all senders.
DMARC policyv=DMARC1; p=none; aspf=r; adkim=r;
DMARC policy is p=none — monitoring only, it does not block spoofed mail. Move to quarantine/reject.
DKIMdefault._domainkey, k2._domainkey
DKIM signing keys found (selectors: default, k2).
MTA-STS
No MTA-STS policy — optional, but it enforces encryption for mail delivery.
SMTP serverGoogle Workspace
Primary mail server responded (Google Workspace).

Recommended improvements

Enforce DMARC with p=quarantine (then p=reject)High
DMARC is published with p=none, so receivers only monitor and spoofed mail claiming this domain is still delivered.
→ Update the DMARC TXT record at _dmarc.roundskysolutions.com to v=DMARC1; p=quarantine; aspf=r; adkim=r; rua=mailto:dmarc@roundskysolutions.com;, monitor for a few weeks, then escalate to p=reject.
90%
impact
Tighten SPF to -allHigh
SPF uses a soft fail (~all), so non-listed senders are only marked neutral and the domain remains spoofable.
→ After confirming all legitimate senders (Google Workspace via +a/+mx, 34.174.196.85, and the dnssmarthost include), change ~all to -all in the existing SPF record.
75%
impact
Enforce strict DKIM alignment (adkim=s)Medium
DMARC uses relaxed DKIM alignment (adkim=r), so a message signed by any domain in your org could authenticate as roundskysolutions.com.
→ Once all outgoing mail is signed under the roundskysolutions.com domain (default/k2 selectors), set adkim=s in the DMARC record.
35%
impact
Add DMARC aggregate reporting (rua)Medium
The DMARC record has no rua tag, so you have no visibility into which senders and third parties are failing authentication.
→ Add rua=mailto:dmarc@roundskysolutions.com (plus ruf for forensics) to the DMARC record before moving away from p=none.
30%
impact
Add an MTA-STS policyLow
Without MTA-STS, inbound delivery can be silently downgraded to plaintext by a stripping attacker.
→ Publish TXT _mta-sts.roundskysolutions.com = v=STSv1; id=20240101; and a policy at https://mta-sts.roundskysolutions.com/.well-known/mta-sts.txt listing mx: aspmx.l.google.com and mx: alt1-4.aspmx.l.google.com with mode: enforce.
25%
impact
Add a TLS-RPT recordLow
Without TLS-RPT you cannot monitor delivery-time TLS failures, so an MTA-STS policy is hard to verify.
→ Publish TXT _smtp._tls.roundskysolutions.com = v=TLSRPTv1; rua=mailto:tlsreport@roundskysolutions.com; to receive failure reports.
15%
impact

Auto-rated from DNS & SMTP records · improvements suggested by AI

Loaded Resources (1 requests · sorted by load time)

Resource	Size	Time	Status
Ffonts.googleapis.com/css?family=Open+Sans:400,700%7CRoboto:400,700	966B	19ms	200

Scan History (1 scans)

Page load time

927ms

TTFB

716ms

Date	TTFB	DOM	Load	Requests	Size	Errors	Scripts
Oct 7, 01:34 PM UTC	716ms	729ms	927ms	1	1KB	0	23AI

Embed a badge

Pick what to show — your detected tech stack, the social-trend valuation, or both.

Badge style

Brand · detected technologies.

Preview

HTML embed

<a href="https://madewith.tech/s/www.roundskysolutions.com"><img src="https://madewith.tech/s/www.roundskysolutions.com/badge.svg" alt="www.roundskysolutions.com on MadeWithTech" /></a>

Markdown

[![www.roundskysolutions.com on MadeWithTech](https://madewith.tech/s/www.roundskysolutions.com/badge.svg)](https://madewith.tech/s/www.roundskysolutions.com)

Share link

https://madewith.tech/s/www.roundskysolutions.com