Website review, no card needed

issoyinc.com logo

issoyinc.com website review

Visit site (opens in a new tab)Reviewed 5 November 202644 issues · 88 checks

This review found 44 issues worth fixing on issoyinc.com, 20 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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

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

How it loaded on a phone

  1. issoyinc.com at 0.7 s0.7 s
  2. issoyinc.com at 1.5 s1.5 s
  3. issoyinc.com at 2.2 s2.2 s
  4. issoyinc.com at 2.9 s2.9 s
  5. issoyinc.com at 3.7 s3.7 s
  6. issoyinc.com at 4.4 s4.4 s
  7. issoyinc.com at 5.1 s5.1 s
  8. issoyinc.com at 5.8 s5.8 s

Speed

7 to fix41
  • Use efficient cache lifetimes

    34.6 s · 14.9 MB

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

  • Improve image delivery

    30.8 s · 13.9 MB

    17 images could be 13.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 30.8 s faster on a phone.

  • Reduce unused JavaScript

    1.1 s · 136 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 41

    41/100

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

  • Reduce unused CSS

    300 ms · 54 KiB

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

  • Minify JavaScript

    300 ms · 34 KiB

    34 KiB could be saved by minifying JavaScript.

  • 9 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Duplicated JavaScript

    13 KiB

    13 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need.

  • Chained critical requests

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

  • Forced reflow

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 29 ms

    29 ms

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

Core Web Vitals

6 to fix34
  • Largest Contentful Paint: 56.2 s

    56.2 s

    Your largest element takes 56.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 58.1 s

    58.1 s

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

  • Cumulative Layout Shift: 0.661

    0.661

    The layout shifts by 0.661 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 7.4 s

    7.4 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 15 images without width and height

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Total Blocking Time: 159 ms

    159 ms

    Scripts block the page for only 159 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix26
  • Page weight: 14.9 MB in 50 requests

    14.9 MB

    Your homepage downloads 14.9 MB in 50 requests on a phone: images 14.4 MB (23), scripts 284 KiB (16) and fonts 112 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 11.8 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    9.4 MB

    6 images are downloaded at several times the size a phone draws them, for example Screenshot-2024-09-19-at-2.52.24 PM.png at 2,998 px wide, shown at 390 px. Resized copies would save about 9.4 MB.

  • 10 images in older formats

    10 images (12.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • An image on the first screen is lazy-loaded

    YxlKJLlBnC8R4liSybskzpTZ3dQWIcgIKk75IWXV.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (86 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.2 g of CO₂ per visit

    4.23 g

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

Accessibility

10 to fixGoogle 7586
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

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

  • Orphan list items

    Some list items are not inside a list.

  • 2 images without alt text

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

  • All page content should be contained by landmarks (10 elements)

    All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

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

  • 14 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

8 to fixGoogle 4659
  • No meta description

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Title is short (11 characters)

    Your title is only 11 characters: “| Issoy Inc”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 2 problems

    Structured data found (Organization) but with 2 problems, for example “Organization: missing name”.

  • No social preview image

    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

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

  • 1 link crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 30 internal links, 0 external

    The homepage links to 30 pages on issoyinc.com and 0 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to Issoy Inc!”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (325 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 11 linked pages hidden from search

    https://issoyinc.com/categories, https://issoyinc.com/categories/consumer-electronics, https://issoyinc.com/categories/cellphone-acessories, https://issoyinc.com/categories/beauty, https://issoyinc.com/categories/toys and https://issoyinc.com/categories/telecom and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://issoyinc.com/categories, https://issoyinc.com/brands, https://issoyinc.com/blog and https://issoyinc.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://issoyinc.com/categories/cellphone-acessories, https://issoyinc.com/categories/beauty, https://issoyinc.com/categories/toys and https://issoyinc.com/categories/telecom use the same meta description. A description written for each page earns more clicks.

  • 12 internal pages checked

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

5 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9697
  • 12 distorted images

    12 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    27 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

  • About 290 words of copy

    The homepage carries about 290 words of visible text.

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Register”, “Contact Us” and “Subscribe”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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 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 issoyinc.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
AWS

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on issoyinc.com, including 13 speed issues, 8 SEO issues and 3 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