Website review, no card needed
dennickfruitsource.com website review
Visit site (opens in a new tab)Reviewed 5 November 202623 issues · 74 checks
This review found 23 issues worth fixing on dennickfruitsource.com, 6 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.8 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Reduce unused JavaScript
1.1 s · 295 KiBAbout 295 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.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 99 KiBAbout 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 138 ms
138 msGoogle Tag Manager costs a phone 138 ms of main-thread work and 300 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.
Improve image delivery
200 ms · 57 KiB4 images could be 57 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
200 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, formcrafts.com and Adobe TypeKit and others), adding 594 KiB and 148 ms of main-thread time.
Use efficient cache lifetimes
200 ms · 6 KiB2 files are served with short cache lifetimes, so returning visitors download them again (6 KiB).
1 long task on the main thread
1 long task block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 384 ms of it running JavaScript. That is comfortably low.
Server response: 112 ms
112 msYour server sent the HTML in 112 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Global Sourcing Expertise You Can Rely On Founded in 2000, …”.
Time to Interactive: 7.7 s
7.7 sThe page becomes fully interactive after 7.7 s. Good is under 3.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.207
0.207The layout shifts by 0.207 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image 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: 28 ms
28 msScripts block the page for only 28 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (42 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (42 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.3 MB in 32 requests
1.3 MBYour homepage downloads 1.3 MB in 32 requests on a phone: scripts 572 KiB (8), images 345 KiB (11) and fonts 161 KiB (5). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
19 tap targets too small
19 tap targets are too small or too close together to hit reliably with a finger.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h5, h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 118 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 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 (115 characters)
Your title is 115 characters, so Google will cut it off around 60: “Dennick FruitSource - Tropical Fruit Ingredient Experts - Imports, Logistics, Supply and …”.
2 H1 headlines
There are 2 <h1> headlines (“Global Sourcing Expertise You Can Rely On” and “Our Global Supply Network”). One clear main headline is easier for people and search engines.
19 internal links, 53 external
The homepage links to 19 pages on dennickfruitsource.com and 53 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Founded in 2000, Dennick FruitSource joined Brothers International in 2021. Led by Nick Filuta, the team operates from …”.
Canonical URL set
The canonical URL is https://dennickfruitsource.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and VideoObject.
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://dennickfruitsource.com/sitemap_index.xml.
AI search readiness
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing url, logo, 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://dennickfruitsource.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 (1,161 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://dennickfruitsource.com/author/clarkras is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://dennickfruitsource.com/author/clarkras has no meta description, so Google writes the search snippet from whatever text it finds.
11 internal pages checked
We fetched 11 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 11 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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
33 of 41 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 602 words of copy
The homepage carries about 602 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”.
1 short form
A short form (3 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 4 customer or partner logos, 4 trust badges and “more than 700 customers”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 8 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
2 cookies set on arrival
2Opening 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.
7 other companies contacted
Loading the homepage contacts 7 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 dennickfruitsource.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- New Dream Network, LLC
Company
- Headquarters
- Tampa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on dennickfruitsource.com, including 11 speed issues, 2 SEO issues and 1 conversion gap. 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.