Website review, no card needed
tootsi.com website review
Visit site (opens in a new tab)Reviewed 25 October 202655 issues · 86 checks
This review found 55 issues worth fixing on tootsi.com, 22 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 95 ms |
| May 9, 2026 | 95 ms |
| May 16, 2026 | 101 ms |
| May 23, 2026 | 109 ms |
| May 30, 2026 | 93 ms |
| Jun 6, 2026 | 86 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 80 ms |
| Jun 27, 2026 | 81 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 114 ms |
| Jul 18, 2026 | 140 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 159 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 82 ms |
| Aug 22, 2026 | 84 ms |
| Aug 29, 2026 | 81 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 92 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 93 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 87 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
Speed
Use efficient cache lifetimes
30.3 s · 10.2 MB68 files are served with short cache lifetimes, so returning visitors download them again (10.2 MB).
Improve image delivery
27.3 s · 9.1 MB13 images could be 9.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 27.3 s faster on a phone.
Reduce unused JavaScript
3.9 s · 768 KiBAbout 768 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Render-blocking requests
2.5 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (jQuery CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.5 MB and 1.7 s of main-thread time.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
jQuery CDN adds 663 ms
663 msjQuery CDN costs a phone 663 ms of main-thread work and 92 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.
Google Tag Manager adds 586 ms
586 msGoogle Tag Manager costs a phone 586 ms of main-thread work and 614 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 370 ms. During a long task the page ignores taps.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 141 ms
141 msGoogle CDN costs a phone 141 ms of main-thread work and 348 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.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 65 but mobile only 39. 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.
Legacy JavaScript
5 KiBPolyfills for old browsers add 5 KiB JavaScript that modern phones do not need.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 52.7 s
52.7 sYour largest element takes 52.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 53.7 s
53.7 sThe page becomes fully interactive after 53.7 s. Good is under 3.8 s.
Speed Index: 12.0 s
12.0 sVisually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 910 ms
910 msScripts block taps and scrolling for 910 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 972 ms
972 msReal visitors wait 972 ms for your server to start answering (75th percentile). Good is under 800 ms.
34 images without width and height
34 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 95 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 105 ms
105 msReal visitors wait 105 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
7 images over 500 KB
7 images weigh 61.5 MB together. On a phone connection a single image that size takes seconds.
Page weight: 11.7 MB in 100 requests
11.7 MBYour homepage downloads 11.7 MB in 100 requests on a phone: images 9.7 MB (44), scripts 1.4 MB (23) and fonts 495 KiB (5). Under 2 MB keeps phones on slow connections fast.
6 images far larger than shown
7.8 MB6 images are downloaded at several times the size a phone draws them, for example banner1-EN.jpg at 2,858 px wide, shown at 390 px. Resized copies would save about 7.8 MB.
15 images in older formats
15 images (62.1 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.
12 images below the first screen load straight away
12 images further down the page (55.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.3 g of CO₂ per visit
3.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.30 g of CO₂e: 396.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
25 images without alt text
25 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
29 links without text
29 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “TOOTSI IMPEX Inc | Supplier of organic and conventional quality bulk foods.”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
6 H1 headlines
There are 6 <h1> headlines (“DISCOVER YUPIK OUR PRE-PACKAGED BRAND”, “DISCOVER ELAN OUR ORGANIC BRAND” and “New Arrivals”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 http://www.tootsi.com/sitemap_tootsi.xml, so Google discovers your pages only by following links.
9 links crawlers can't follow
9 links have no real href, so search engines can't follow them.
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 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.
77 internal links, 1 external
The homepage links to 77 pages on tootsi.com and 1 external page.
2 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Wholesale supplier and manufacturer of organic and conventional nuts, dried fruits, grains, seeds, superfoods, snacks, …”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
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://tootsi.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 (213 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
30 small tap targets
30 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “n(...).live is not a function”.
19 low-resolution images
19 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 225 words
The homepage has only about 225 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.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Register”, “Order Request” and “Contact us”.
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
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.
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 tootsi.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 55 issues on tootsi.com, including 22 speed issues, 9 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.