Website review, no card needed

thisism.com logo

thisism.com website review

Visit site (opens in a new tab)Reviewed 5 November 202636 issues · 71 checks

This review found 36 issues worth fixing on thisism.com, 10 of them high impact, across 71 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.8 s3.7 sMay 16Oct 313.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.7 s
Jul 25, 20263.7 s
Aug 1, 20263.7 s
Aug 8, 20263.7 s
Aug 15, 20263.7 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.8 s
Oct 24, 20263.8 s
Oct 31, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
312 ms302 msMay 16Oct 31306 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026306 ms
May 23, 2026306 ms
May 30, 2026307 ms
Jun 6, 2026311 ms
Jun 13, 2026311 ms
Jun 20, 2026311 ms
Jun 27, 2026310 ms
Jul 4, 2026307 ms
Jul 11, 2026305 ms
Jul 18, 2026304 ms
Jul 25, 2026303 ms
Aug 1, 2026303 ms
Aug 8, 2026303 ms
Aug 15, 2026303 ms
Aug 22, 2026304 ms
Aug 29, 2026305 ms
Sep 5, 2026305 ms
Sep 12, 2026305 ms
Sep 19, 2026305 ms
Sep 26, 2026304 ms
Oct 3, 2026305 ms
Oct 10, 2026305 ms
Oct 17, 2026305 ms
Oct 24, 2026306 ms
Oct 31, 2026306 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of thisism.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thisism.com at 0.4 s0.4 s
  2. thisism.com at 0.8 s0.8 s
  3. thisism.com at 1.1 s1.1 s
  4. thisism.com at 1.5 s1.5 s
  5. thisism.com at 1.9 s1.9 s
  6. thisism.com at 2.3 s2.3 s
  7. thisism.com at 2.6 s2.6 s
  8. thisism.com at 3.0 s3.0 s

Speed

3 to fix79
  • Reduce unused JavaScript

    150 ms · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Mobile performance score: 79

    79/100

    Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    224 KiB

    About 224 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    150 ms · 25 KiB

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

  • Font display

    50 ms

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Facebook), adding 5 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 747 ms of it running JavaScript. That is comfortably low.

  • Server response: 172 ms

    172 ms

    Your server sent the HTML in 172 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 12.1 s

    12.1 s

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

  • Total Blocking Time: 606 ms

    606 ms

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 323 ms

    323 ms

    Real visitors wait 323 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Speed Index: 4.5 s

    4.5 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 306 ms to 306 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 2.5 s

    2.5 s

    Your largest element renders in 2.5 s on a phone, inside Google's 2.5 s “good” threshold.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix67
  • Page weight: 2.3 MB in 30 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 30 requests on a phone: scripts 1.7 MB (14), stylesheets 216 KiB (1) and fonts 181 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 0.6 g of CO₂ per visit

    0.64 g

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

Accessibility

5 to fixGoogle 8668
  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • [role]s do not have all required [aria-*] attributes

    [role]s do not have all required [aria-*] attributes (1 element).

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

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

1 checks passed
  • 6 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 9 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 6955
  • robots.txt blocks all crawlers

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

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (9 characters)

    Your title is only 9 characters: “Instagram”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No XML sitemap

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 9 internal links, 10 external

    The homepage links to 9 pages on thisism.com and 10 external pages.

2 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Create an account or log in to Instagram - Share what you're into with the people who get you.”.

  • Canonical URL set

    The canonical URL is https://www.instagram.com/.

AI search readiness

2 to fix37
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    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.

  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.instagram.com/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.

  • Opted out of AI training for 5 crawlers

    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.

Other pages

3 to fix83
  • 3 pages share a title

    https://www.instagram.com/accounts/login?next=https%3A%2F%2Fwww.instagram.com%2Fmpublishing_%2F&is_from_rle, https://www.instagram.com/explore/locations and https://www.instagram.com/web/lite all use the title “Instagram”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.instagram.com/legal/terms, https://www.instagram.com/explore/locations and https://www.instagram.com/web/lite have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.instagram.com/legal/privacy, https://www.instagram.com/legal/terms, https://www.instagram.com/explore/locations, https://www.instagram.com/popular and https://www.instagram.com/web/lite have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 internal pages checked

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

4 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8189
  • Deprecated browser APIs

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “ErrorUtils caught an error: Cannot read properties of undefined (reading 'ready') Subsequent non-fatal errors won't be …”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • No call to action on the first screen

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

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

  • Only about 91 words

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

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

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Uploading & Non-Users”.

  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at thisism.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Namecheap

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on thisism.com, including 12 speed issues, 6 SEO issues and 5 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25