workintexas.com website review

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

35 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.

About 535 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

The HTML itself could arrive about 2.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your mobile performance score is 39 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page goes through 2 redirects before it starts loading, costing about 960 ms. Link and advertise the final URL directly.

6 images could be 316 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

68 KiB could be saved by minifying JavaScript.

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

29 KiB could be saved by minifying CSS.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

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

3 third-party services load with your homepage (Google Tag Manager, geosolinc.com and Google Analytics), adding 498 KiB and 403 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

The first text or image appears after 7.9 s on a phone. Good is under 1.8 s.

Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Man looking at a laptop.”.

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

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

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

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

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

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

9 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 2.6 MB in 71 requests on a phone: scripts 1.3 MB (30), fonts 596 KiB (2) and images 462 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

button, link, and menuitem elements do not have accessible names. (1 element).

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

The robots meta tag says “NOINDEX, NOFOLLOW”: Google is told not to list this page at all.

Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://workintexas.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no /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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

A form field blocks pasting, which frustrates password managers and people on phones.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No character set is declared, so some characters can render as gibberish.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 6 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

workintexas.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

workintexas.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

workintexas.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

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.

Opening the homepage sets 5 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.