Website review, no card needed
frankotrading.com website review
Visit site (opens in a new tab)Reviewed 23 October 202650 issues · 76 checks
This review found 50 issues worth fixing on frankotrading.com, 25 of them high impact, across 76 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
52FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 8.2 s |
| May 9, 2026 | 8.2 s |
| May 16, 2026 | 8.1 s |
| May 23, 2026 | 8.1 s |
| May 30, 2026 | 8.1 s |
| Jun 6, 2026 | 8.1 s |
| Jun 13, 2026 | 8.2 s |
| Jun 20, 2026 | 8.2 s |
| Jun 27, 2026 | 8.3 s |
| Jul 4, 2026 | 8.3 s |
| Jul 11, 2026 | 8.3 s |
| Jul 18, 2026 | 8.2 s |
| Jul 25, 2026 | 8.1 s |
| Aug 1, 2026 | 8.0 s |
| Aug 8, 2026 | 7.9 s |
| Aug 15, 2026 | 7.9 s |
| Aug 22, 2026 | 7.9 s |
| Aug 29, 2026 | 8.0 s |
| Sep 5, 2026 | 8.0 s |
| Sep 12, 2026 | 8.0 s |
| Sep 19, 2026 | 8.0 s |
| Sep 26, 2026 | 8.0 s |
| Oct 3, 2026 | 8.1 s |
| Oct 10, 2026 | 8.1 s |
| Oct 17, 2026 | 8.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 794 ms |
| May 9, 2026 | 781 ms |
| May 16, 2026 | 782 ms |
| May 23, 2026 | 787 ms |
| May 30, 2026 | 796 ms |
| Jun 6, 2026 | 798 ms |
| Jun 13, 2026 | 782 ms |
| Jun 20, 2026 | 771 ms |
| Jun 27, 2026 | 753 ms |
| Jul 4, 2026 | 753 ms |
| Jul 11, 2026 | 754 ms |
| Jul 18, 2026 | 745 ms |
| Jul 25, 2026 | 765 ms |
| Aug 1, 2026 | 772 ms |
| Aug 8, 2026 | 803 ms |
| Aug 15, 2026 | 804 ms |
| Aug 22, 2026 | 785 ms |
| Aug 29, 2026 | 775 ms |
| Sep 5, 2026 | 770 ms |
| Sep 12, 2026 | 790 ms |
| Sep 19, 2026 | 816 ms |
| Sep 26, 2026 | 836 ms |
| Oct 3, 2026 | 830 ms |
| Oct 10, 2026 | 822 ms |
| Oct 17, 2026 | 807 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
How it loaded on a phone
0.8 s
1.7 s
2.5 s
3.4 s
4.2 s
5.0 s
5.9 s
6.7 s
Speed
Use efficient cache lifetimes
8.4 s · 25.8 MB74 files are served with short cache lifetimes, so returning visitors download them again (25.8 MB).
Improve image delivery
8.7 s · 25.5 MB88 images could be 25.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.7 s faster on a phone.
Reduce unused JavaScript
6.1 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.1 s faster on a phone.
Mobile performance score: 27
27/100Your mobile performance score is 27 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 4.3 MB and 1.4 s of main-thread time.
Render-blocking requests
950 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Google Tag Manager adds 860 ms
860 msGoogle Tag Manager costs a phone 860 ms of main-thread work and 894 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 454 ms. During a long task the page ignores taps.
Amazon Web Services adds 3 ms
3 msAmazon Web Services costs a phone 3 ms of main-thread work and 2.9 MB 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.
Facebook adds 257 ms
257 msFacebook costs a phone 257 ms of main-thread work and 255 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.
2,201 HTML elements
The page has 2,201 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
140 ms · 16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
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.
Real-user LCP: 6.3 s
6.3 sReal visitors wait 6.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 791 ms
791 msReal visitors wait 791 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 3.0 s
3.0 sReal visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 9.4 s
9.4 sThe first text or image appears after 9.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 48.0 s
48.0 sYour largest element takes 48.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Franko Trading”.
Time to Interactive: 49.0 s
49.0 sThe page becomes fully interactive after 49.0 s. Good is under 3.8 s.
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Real-user TTFB: 924 ms
924 msReal visitors wait 924 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.131
0.131The layout shifts by 0.131 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 794 ms to 807 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-17, real Chrome visitors' largest content (lcp) went from 8.2 s to 8.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 31.6 MB in 160 requests
31.6 MBYour homepage downloads 31.6 MB in 160 requests on a phone: images 26.2 MB (91), other files 2.9 MB (47) and scripts 2.4 MB (14). Under 2 MB keeps phones on slow connections fast.
40 images far larger than shown
18.0 MB40 images are downloaded at several times the size a phone draws them, for example 9d137c01f81c40fe84138182f218eadefd1013_ii.png at 1,254 px wide, shown at 138 px. Resized copies would save about 18.0 MB.
13 images over 500 KB
13 images weigh 11.7 MB together. On a phone connection a single image that size takes seconds.
40 images in older formats
40 images (20.6 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.
29 images below the first screen load straight away
29 images further down the page (14.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 9.0 g of CO₂ per visit
8.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.96 g of CO₂e: 1074.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (187 elements)
All page content should be contained by landmarks: 187 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.
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 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (116 characters)
Your title is 116 characters, so Google will cut it off around 60: “Franko Trading Enterprise - Quality Phones, Laptops, Fridges & Electronics in Ghana | Bes…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (256 characters)
Your meta description is 256 characters; Google truncates after about 160, so the end of your pitch is cut.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
4 checks passed
Canonical URL set
The canonical URL is https://www.frankotrading.com/.
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.frankotrading.com/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
2%A phone browser shows 667 words, but the HTML your server sends has only 15. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.frankotrading.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.
1 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.
Best practices
15 small tap targets
15 of 43 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 667 words of copy
The homepage carries about 667 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Now”.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
16 other companies contacted
Loading the homepage contacts 16 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 frankotrading.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on frankotrading.com, including 24 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.