Website review, no card needed

ssi.shimadzu.com logo

ssi.shimadzu.com website review

Visit site (opens in a new tab)Reviewed 26 October 202635 issues · 89 checks

This review found 35 issues worth fixing on ssi.shimadzu.com, 13 of them high impact, across 89 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

Real-visitor load time (LCP)75th percentile, phones
3.2 s2.3 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.1 s
May 9, 20263.1 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.0 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
151 ms102 msMay 2Oct 17108 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026129 ms
May 9, 2026124 ms
May 16, 2026122 ms
May 23, 2026123 ms
May 30, 2026130 ms
Jun 6, 2026142 ms
Jun 13, 2026145 ms
Jun 20, 2026136 ms
Jun 27, 2026133 ms
Jul 4, 2026129 ms
Jul 11, 2026122 ms
Jul 18, 2026123 ms
Jul 25, 2026118 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026116 ms
Aug 22, 2026122 ms
Aug 29, 2026126 ms
Sep 5, 2026130 ms
Sep 12, 2026134 ms
Sep 19, 2026135 ms
Sep 26, 2026129 ms
Oct 3, 2026124 ms
Oct 10, 2026113 ms
Oct 17, 2026108 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 ssi.shimadzu.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix50
  • Use efficient cache lifetimes

    8.4 s · 1.5 MB

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

  • Render-blocking requests

    4.5 s

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

  • Reduce unused JavaScript

    3.3 s · 747 KiB

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

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50 (desktop: 77). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Gigya and Hubspot and others), adding 1.3 MB and 752 ms of main-thread time.

  • Google Tag Manager adds 410 ms

    410 ms

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

  • Legacy JavaScript

    400 ms · 78 KiB

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

  • Duplicated JavaScript

    300 ms · 44 KiB

    44 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.2 s

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

  • Improve image delivery

    243 KiB

    10 images could be 243 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 59 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 77 but mobile only 50. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 10.4 s

    10.4 s

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

  • Largest Contentful Paint: 23.4 s

    23.4 s

    Your largest element takes 23.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “GCMS-TQ RX Series Triple Quadrupole GC-MS”.

  • Time to Interactive: 23.6 s

    23.6 s

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

  • Speed Index: 10.4 s

    10.4 s

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

  • Total Blocking Time: 286 ms

    286 ms

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

  • 8 images without width and height

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 93 ms

    93 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 523 ms

    523 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Cumulative Layout Shift: 0.04

    0.04

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 152 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 152 requests on a phone: scripts 1.6 MB (51), fonts 686 KiB (5) and images 442 KiB (35). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.85 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8389
  • 1 text element with low contrast

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

  • Frames without titles

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

  • 9 links without text

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9287
  • No H1 headline

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

  • No favicon declared

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 52 internal links, 19 external

    The homepage links to 52 pages on ssi.shimadzu.com and 19 external pages.

7 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Discover insights and innovative solutions from Shimadzu, tailored to your needs. Visit Shimadzu today for more informa…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Analytical Testing / Measuring Instruments | Shimadzu”.

  • Canonical URL set

    The canonical URL is https://www.ssi.shimadzu.com/.

  • Structured data in place

    Structured data found: Organization and WebPage.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.ssi.shimadzu.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://www.ssi.shimadzu.com/products/molecular-spectroscopy/ftir/70th-anniversary/index.html has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ssi.shimadzu.com/service-support/index.html, whose canonical is https://www.ssi.shimadzu.com/industries/forensics/index.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.ssi.shimadzu.com/products/molecular-spectroscopy/ftir/70th-anniversary/index.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

  • 12 small tap targets

    12 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

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

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • 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 471 words of copy

    The homepage carries about 471 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request More Info” and “Register Now!”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Request More Info”, “Register Now!” and “Contact a Sales Rep”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 4 of them by other companies (measured from a US location before any click).

  • 45 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 ssi.shimadzu.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on ssi.shimadzu.com, including 15 speed issues, 3 SEO issues and 4 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