Catalog / redhousetechnology.com
57

SEO audit for redhousetechnology.com

RedHouse Technology - Integrating Global Solutions

saas

Health 57/100 (fair) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

RedHouse Technology creates affordable, up to date, customer friendly web sites. Pricing, samples, and testimonials on site.

Screenshot of redhousetechnology.com
50
pages crawled
47
indexable pages
8
errors
376
warnings
577
notices
0
orphan pages
5
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Links 90 5 0 47
Crawlability 94 3 0 0
Duplicate 58 0 70 47
Agent Readiness 72 0 47 48
Canonical 72 0 47 0
Images 72 0 47 0
Mobile 72 0 47 47
Security 72 0 47 4
Performance 73 0 45 94
Content 84 0 26 118
Sitemap 100 0 0 23
Social 100 0 0 94
Structured Data 100 0 0 47
URL 100 0 0 8
Findings

Errors (2 rules)

error Broken internal link (target 4xx/5xx)

Rule links.broken_internal · Links · 5 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 3 occurrence(s)

Warnings (10 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 47 occurrence(s)

warning Missing canonical tag

Rule canonical.missing · Canonical · 47 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 26 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 20 occurrence(s)

warning Homepage duplicated across protocol/host variants (no redirect)

Rule duplicate.protocol_host · Duplicate · 3 occurrence(s)

  • http://redhousetechnology.com/ — http://www.redhousetechnology.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
  • http://redhousetechnology.com/ — https://redhousetechnology.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.
  • http://redhousetechnology.com/ — https://www.redhousetechnology.com/ serves the same homepage content with a 200 and no redirect — Google sees a duplicate. Pick one canonical host/scheme and 301-redirect the others.

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 47 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 47 occurrence(s)

  • http://redhousetechnology.com/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/about.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/careers.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/casestudies.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/clientlogin.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/contactus.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/helpfullinks.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/management.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/news_article_030501.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/news_article_030708.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/news_article_040601.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/news_article_060515.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/newsarchive.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/ourapproach.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/ourclients.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/outsourcing.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/partners.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/portalsolutions.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/projectoffice.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/requestinfo.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/solutions.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/technologoperationsystrategy.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/content/whatwedo.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • http://www.redhousetechnology.com/index.htm — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Images missing alt text

Rule images.missing_alt · Images · 47 occurrence(s)

warning Missing viewport meta tag

Rule mobile.viewport_missing · Mobile · 47 occurrence(s)

warning Render-blocking script in <head> (no defer/async)

Rule perf.render_blocking · Performance · 45 occurrence(s)

Notices (16 rules)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 47 occurrence(s)

notice Main text is hard to read (low Flesch Reading Ease)

Rule content.readability_poor · Content · 39 occurrence(s)

  • http://redhousetechnology.com/ — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://redhousetechnology.com/content/management.htm — this page reads as very difficult (Flesch Reading Ease 25, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://redhousetechnology.com/content/ourapproach.htm — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://redhousetechnology.com/content/partners.htm — this page reads as very difficult (Flesch Reading Ease 17, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://redhousetechnology.com/content/whatwedo.htm — this page reads as very difficult (Flesch Reading Ease -10, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/ — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/about.htm — this page reads as very difficult (Flesch Reading Ease 10, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/careers.htm — this page reads as difficult (Flesch Reading Ease 36, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/casestudies.htm — this page reads as very difficult (Flesch Reading Ease 15, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/management.htm — this page reads as very difficult (Flesch Reading Ease 25, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/news_article_030501.htm — this page reads as very difficult (Flesch Reading Ease 16, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/news_article_030708.htm — this page reads as very difficult (Flesch Reading Ease 16, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/news_article_040601.htm — this page reads as very difficult (Flesch Reading Ease 10, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/news_article_060515.htm — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/newsarchive.htm — this page reads as very difficult (Flesch Reading Ease 9, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/ourapproach.htm — this page reads as very difficult (Flesch Reading Ease 20, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/ourclients.htm — this page reads as very difficult (Flesch Reading Ease 29, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/outsourcing.htm — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/partners.htm — this page reads as very difficult (Flesch Reading Ease 17, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/portalsolutions.htm — this page reads as very difficult (Flesch Reading Ease 17, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/projectoffice.htm — this page reads as very difficult (Flesch Reading Ease 4, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/solutions.htm — this page reads as very difficult (Flesch Reading Ease -10, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/technologoperationsystrategy.htm — this page reads as very difficult (Flesch Reading Ease 8, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/content/whatwedo.htm — this page reads as very difficult (Flesch Reading Ease -10, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.
  • http://www.redhousetechnology.com/index.htm — this page reads as very difficult (Flesch Reading Ease 24, below 50) — long sentences and multi-syllable words make it hard to scan. Shorten sentences and prefer plainer words to widen your audience. Density can be legitimate for expert, technical or legal content, so judge it against who the page is for.

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 47 occurrence(s)

notice Missing <!DOCTYPE html> (quirks-mode rendering risk)

Rule encoding.doctype_missing · Content · 32 occurrence(s)

notice Missing html lang attribute

Rule i18n.lang_missing · Mobile · 47 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 47 occurrence(s)

  • http://redhousetechnology.com/ — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/ — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/about.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/careers.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/casestudies.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/clientlogin.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/contactus.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/helpfullinks.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/management.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/news_article_030501.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/news_article_030708.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/news_article_040601.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/news_article_060515.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/newsarchive.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/ourapproach.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/ourclients.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/outsourcing.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/partners.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/portalsolutions.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/projectoffice.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/requestinfo.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/solutions.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/technologoperationsystrategy.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/content/whatwedo.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • http://www.redhousetechnology.com/index.htm — the likely hero/LCP image (redhouselogo.gif) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Internal link has no anchor text / accessible name

Rule links.no_anchor_text · Links · 47 occurrence(s)

notice Legacy <meta name=keywords> tag present (Google ignores it)

Rule meta.keywords_present · Content · 47 occurrence(s)

notice Missing Open Graph tags

Rule og.missing · Social · 47 occurrence(s)

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 47 occurrence(s)

notice No structured data detected

Rule schema.none · Structured Data · 47 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 4 occurrence(s)

notice Indexable page not listed in sitemap

Rule sitemap.orphan_not_listed · Sitemap · 23 occurrence(s)

notice Missing Twitter Card tag

Rule twitter.missing · Social · 47 occurrence(s)

notice Underscores in URL path (prefer hyphens)

Rule url.underscores · URL · 8 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
http://www.redhousetechnology.com/content/about.htm
RedHouse Technology - Anout Us		 200 yes 195 24
http://www.redhousetechnology.com/content/careers.htm
RedHouse Technology - Careers		 200 yes 152 24
http://www.redhousetechnology.com/content/casestudies.htm
RedHouse Technology - Case Studies		 200 yes 172 24
http://www.redhousetechnology.com/content/clientlogin.htm
RedHouse Technology - Client Login		 200 yes 97 24
http://www.redhousetechnology.com/content/contactus.htm
RedHouse Technology - Contact Us		 200 yes 80 24
http://www.redhousetechnology.com/content/helpfullinks.htm
RedHouse Technology - Helpful Links		 200 yes 92 24
http://www.redhousetechnology.com/content/management.htm
RedHouse Technology - Management Team		 200 yes 606 24
http://www.redhousetechnology.com/content/newsarchive.htm
RedHouse Technology - News Archive		 200 yes 118 24
http://www.redhousetechnology.com/content/ourapproach.htm
RedHouse Technology - Our Approach		 200 yes 180 24
http://www.redhousetechnology.com/content/ourclients.htm
RedHouse Technology - Our Clients		 200 yes 106 24
http://www.redhousetechnology.com/content/outsourcing.htm
RedHouse Technology - Outsourcing Services		 200 yes 366 24
http://www.redhousetechnology.com/content/partners.htm
RedHouse Technology - Valued Partners		 200 yes 132 24
http://www.redhousetechnology.com/content/portalsolutions.htm
RedHouse Technology - Portal Solutions		 200 yes 372 24
http://www.redhousetechnology.com/content/projectoffice.htm
RedHouse Technology - Project Office		 200 yes 502 24
http://www.redhousetechnology.com/content/requestinfo.htm
RedHouse Technology - Request Information		 200 yes 59 24
http://www.redhousetechnology.com/content/solutions.htm
RedHouse Technology - Solution Areas		 200 yes 228 24
http://www.redhousetechnology.com/content/technologoperationsystrategy.htm
RedHouse Technology - Technology Operations Strategy		 200 yes 293 24
http://www.redhousetechnology.com/content/whatwedo.htm
RedHouse Technology - What We Do		 200 yes 213 24
http://redhousetechnology.com/content/about.htm
RedHouse Technology - Anout Us		 200 yes 195 23
http://redhousetechnology.com/content/careers.htm
RedHouse Technology - Careers		 200 yes 152 23
http://redhousetechnology.com/content/casestudies.htm
RedHouse Technology - Case Studies		 200 yes 172 23
http://redhousetechnology.com/content/clientlogin.htm
RedHouse Technology - Client Login		 200 yes 97 23
http://redhousetechnology.com/content/contactus.htm
RedHouse Technology - Contact Us		 200 yes 80 23
http://redhousetechnology.com/content/helpfullinks.htm
RedHouse Technology - Helpful Links		 200 yes 92 23
http://redhousetechnology.com/content/management.htm
RedHouse Technology - Management Team		 200 yes 606 23
http://redhousetechnology.com/content/newsarchive.htm
RedHouse Technology - News Archive		 200 yes 118 23
http://redhousetechnology.com/content/ourapproach.htm
RedHouse Technology - Our Approach		 200 yes 180 23
http://redhousetechnology.com/content/ourclients.htm
RedHouse Technology - Our Clients		 200 yes 106 23
http://redhousetechnology.com/content/outsourcing.htm
RedHouse Technology - Outsourcing Services		 200 yes 366 23
http://redhousetechnology.com/content/partners.htm
RedHouse Technology - Valued Partners		 200 yes 132 23
http://redhousetechnology.com/content/portalsolutions.htm
RedHouse Technology - Portal Solutions		 200 yes 372 23
http://redhousetechnology.com/content/projectoffice.htm
RedHouse Technology - Project Office		 200 yes 502 23
http://redhousetechnology.com/content/requestinfo.htm
RedHouse Technology - Request Information		 200 yes 59 23
http://redhousetechnology.com/content/solutions.htm
RedHouse Technology - Solution Areas		 200 yes 228 23
http://redhousetechnology.com/content/technologoperationsystrategy.htm
RedHouse Technology - Technology Operations Strategy		 200 yes 293 23
http://redhousetechnology.com/content/whatwedo.htm
RedHouse Technology - What We Do		 200 yes 213 23
http://www.redhousetechnology.com/index.htm
RedHouse Technology - Integrating Global Solutions		 200 yes 156 22
http://redhousetechnology.com/index.htm
RedHouse Technology - Integrating Global Solutions		 200 yes 156 21
http://www.redhousetechnology.com/content/news_article_030501.htm
RedHouse Technology - News		 200 yes 410 7
http://redhousetechnology.com/content/news_article_030501.htm
RedHouse Technology - News		 200 yes 410 6
http://www.redhousetechnology.com/content/news_article_060515.htm
RedHouse Technology - Ralph Bailets joins RedHouse Technology		 200 yes 382 5
http://redhousetechnology.com/content/news_article_060515.htm
RedHouse Technology - Ralph Bailets joins RedHouse Technology		 200 yes 382 4
http://redhousetechnology.com/content/news_article_030708.htm
RedHouse Technology - News		 200 yes 382 2
http://www.redhousetechnology.com/content/news_article_030708.htm
RedHouse Technology - News		 200 yes 382 2
http://www.redhousetechnology.com/content/news_article_040601.htm
RedHouse Technology - News		 200 yes 200 1
http://redhousetechnology.com/
RedHouse Technology - Integrating Global Solutions		 200 yes 156 0
http://www.redhousetechnology.com/
RedHouse Technology - Integrating Global Solutions		 200 yes 156 0
http://redhousetechnology.com/index.html 404 no 17 2
http://www.redhousetechnology.com/content/news_article_050515.htm 404 no 17 1
http://www.redhousetechnology.com/index.html 404 no 17 2

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →