timeinsheets.com website review

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

19 files are served with short cache lifetimes, so returning visitors download them again (103 KiB).

Google CDN costs a phone 126 ms of main-thread work and 349 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.

About 243 KiB of JavaScript is downloaded but never used on this page.

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

About 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

4 third-party services load with your homepage (Google CDN, FontAwesome CDN and Other Google APIs/SDKs and others), adding 474 KiB and 131 ms of main-thread time.

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

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.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

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.

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

1 dropdown has no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate 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.

5 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

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

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

Google's crawler is blocked from indexing this page.

Your title is only 21 characters: “Home | WS Co 84926497”. Between 30 and 65 characters leaves room to say what you do and for whom.

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.

Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 20 pages on timeinsheets.com and 4 external pages.

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.

/page/how-it-works has no meta description, so Google writes the search snippet from whatever text it finds.

/features, /pricing, /contact, /page/terms-of-use and /page/privacy-policy use the same meta description. A description written for each page earns more clicks.

/features, /pricing, /contact, /page/how-it-works, /page/terms-of-use and /page/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

/contact has 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.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

10 images failed to load on a phone, for example https://timeinsheets-bucket.s3.us-east-2.amazonaws.com/app-logo/c39bf824831869a3337cfc9461eedba4.png?X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAYJOAMT2.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.0.8/css/all.css' from origin 'https://timeinsheets…”.

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.

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

The homepage carries about 950 words of visible text.

Opening the homepage sets 2 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.