Website review, no card needed
aliteprojects.com website review
Visit site (opens in a new tab)Reviewed 25 October 202633 issues · 86 checks
This review found 33 issues worth fixing on aliteprojects.com, 11 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.1 s |
| May 9, 2026 | 1.2 s |
| May 16, 2026 | 1.2 s |
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 102 ms |
| May 9, 2026 | 110 ms |
| May 16, 2026 | 109 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 109 ms |
| Jul 18, 2026 | 107 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 101 ms |
| Aug 8, 2026 | 101 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 101 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 115 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 99 ms |
| Oct 3, 2026 | 97 ms |
| Oct 10, 2026 | 95 ms |
| Oct 17, 2026 | 93 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
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.3 s
7.4 s
8.4 s
Speed
Use efficient cache lifetimes
3.3 s · 10.1 MB25 files are served with short cache lifetimes, so returning visitors download them again (10.1 MB).
Render-blocking requests
3.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.
Reduce unused JavaScript
1.5 s · 977 KiBAbout 977 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Reduce unused CSS
1.1 s · 177 KiBAbout 177 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.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Google Tag Manager and Hotjar and others), adding 2.0 MB and 916 ms of main-thread time.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 62). Pages that score under 90 lose visitors before the first paint.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Google CDN adds 371 ms
371 msGoogle CDN costs a phone 371 ms of main-thread work and 1.1 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.
Legacy JavaScript
300 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 248 ms
248 msGoogle Tag Manager costs a phone 248 ms of main-thread work and 552 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 17 KiB17 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 104 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.
1 checks passed
Server response: 253 ms
253 msYour server sent the HTML in 253 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Think Partner, Not Agency. When you partner with us, you’ll…”.
Speed Index: 14.3 s
14.3 sVisually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 234 ms
234 msScripts block taps and scrolling for 234 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 115 ms
115 msReal visitors wait 115 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
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.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 102 ms to 93 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.033
0.033The layout barely moves while loading (CLS 0.033, good is under 0.1).
Images and page weight
Page weight: 12.4 MB in 59 requests
12.4 MBYour homepage downloads 12.4 MB in 59 requests on a phone: media 9.3 MB (5), scripts 2.0 MB (19) and other files 351 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (69 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.
About 3.5 g of CO₂ per visit
3.52 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.52 g of CO₂e: 422.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
21 buttons without a name
21 buttons have no accessible name, so screen readers announce just “button”.
21 text elements with low contrast
21 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 (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h2 → h4, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Full-Service Web Design, Development & Performance Marketing Agency - AliteProjects”.
Meta description is long (183 characters)
Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
44 internal links, 6 external
The homepage links to 44 pages on aliteprojects.com and 6 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Full-Service Web Design & Performance Marketing Agency”.
Canonical URL set
The canonical URL is https://www.aliteprojects.com/.
Structured data in place
Structured data found: LocalBusiness.
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.aliteprojects.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.aliteprojects.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (969 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.aliteprojects.com/blog.html 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://www.aliteprojects.com/blog.html has no meta description, so Google writes the search snippet from whatever text it finds.
14 links to non-canonical URLs
Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://www.aliteprojects.com/about-us.html, whose canonical is https://www.aliteprojects.com/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages slow to respond
https://www.aliteprojects.com/about-us.html, https://www.aliteprojects.com/services.html, https://www.aliteprojects.com/portfolio.html, https://www.aliteprojects.com/work-model.html, https://www.aliteprojects.com/blog.html and https://www.aliteprojects.com/contact-us.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 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”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 18 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 947 words of copy
The homepage carries about 947 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get In Touch”.
6 calls to action
The homepage has 6 calls to action, for example “Contact”, “Get In Touch” and “Join us to "Be a Solution Deliverer"!”.
2 short forms
2 short forms (7 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Hotjar.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
12 other companies contacted
Loading the homepage contacts 12 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 aliteprojects.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on aliteprojects.com, including 17 speed issues, 3 SEO issues and 2 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.