Website review, no card needed
applefactory.com.gt website review
Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 72 checks
This review found 28 issues worth fixing on applefactory.com.gt, 8 of them high impact, across 72 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
71CClosest 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.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Reduce unused CSS
1.1 s · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
504 KiBAbout 504 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 288 ms. During a long task the page ignores taps.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Use efficient cache lifetimes
150 ms · 40 KiB6 files are served with short cache lifetimes, so returning visitors download them again (40 KiB).
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 11 KiB11 KiB could be saved by minifying CSS.
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 106 KiB and 12 ms of main-thread time.
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: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 285 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.395
0.395The layout shifts by 0.395 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 8.7 s
8.7 sThe page becomes fully interactive after 8.7 s. Good is under 3.8 s.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Journey Starts Here,”.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Speed Index: 4.2 s
4.2 sVisually, the page fills in at 4.2 s (Speed Index). Good is under 3.4 s.
5 images without width and height
5 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: 179 ms
179 msScripts block the page for only 179 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
01-icono-jumbo.webp 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).
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.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.3 MB in 23 requests
1.3 MBYour homepage downloads 1.3 MB in 23 requests on a phone: scripts 921 KiB (4), fonts 180 KiB (5) and stylesheets 151 KiB (3). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Home | AppleFactory”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 short (35 characters)
Your meta description is only 35 characters: “This is the homepage of the website”. 70 to 160 characters is enough to sell the click.
One H1 headline
Your <h1> is empty.
31 internal links, 2 external
The homepage links to 31 pages on applefactory.com.gt and 2 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.applefactory.com.gt/.
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.applefactory.com.gt/sitemap.xml.
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://www.applefactory.com.gt/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Other pages
3 linked pages are broken
Your homepage links to https://www.applefactory.com.gt/website/social/facebook, https://www.applefactory.com.gt/website/social/twitter and https://www.applefactory.com.gt/website/social/linkedin, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages share 2 titles
/ and https://www.applefactory.com.gt/es_GT all use the title “Home | AppleFactory”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.applefactory.com.gt/shop, https://www.applefactory.com.gt/blog, https://www.applefactory.com.gt/jobs and https://www.applefactory.com.gt/shop/wishlist have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.applefactory.com.gt/blog, whose canonical is https://www.applefactory.com.gt/blog/our-blog-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.applefactory.com.gt/shop, https://www.applefactory.com.gt/blog, https://www.applefactory.com.gt/jobs and https://www.applefactory.com.gt/shop/wishlist have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.applefactory.com.gt/blog and https://www.applefactory.com.gt/es_GT have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
2 pages slow to respond
https://www.applefactory.com.gt/blog and https://www.applefactory.com.gt/shop/wishlist took over 3 s to send their HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
10 small tap targets
10 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 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.
Only about 104 words
The homepage has only about 104 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.
4 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Shop”, “Contact us” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Umami and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
3 cookies set on arrival
3Opening the homepage sets 3 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 applefactory.com.gt, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on applefactory.com.gt, including 11 speed issues, 4 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.