Website review, no card needed
smartling.com website review
Visit site (opens in a new tab)Reviewed 29 October 202624 issues · 100 checks
This review found 24 issues worth fixing on smartling.com, 6 of them high impact, across 100 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
88BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 310 ms |
| May 16, 2026 | 316 ms |
| May 23, 2026 | 305 ms |
| May 30, 2026 | 273 ms |
| Jun 6, 2026 | 238 ms |
| Jun 13, 2026 | 211 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 193 ms |
| Jul 4, 2026 | 197 ms |
| Jul 11, 2026 | 211 ms |
| Jul 18, 2026 | 221 ms |
| Jul 25, 2026 | 216 ms |
| Aug 1, 2026 | 217 ms |
| Aug 8, 2026 | 224 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 227 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 226 ms |
| Sep 19, 2026 | 230 ms |
| Sep 26, 2026 | 238 ms |
| Oct 3, 2026 | 238 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 234 ms |
| Oct 24, 2026 | 225 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
Render-blocking requests
1.0 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Use efficient cache lifetimes
350 ms · 261 KiB73 files are served with short cache lifetimes, so returning visitors download them again (261 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Hubspot and others), adding 538 KiB and 536 ms of main-thread time.
1,631 HTML elements
The page has 1,631 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Reduce unused JavaScript
124 KiBAbout 124 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
98 KiBAbout 98 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
74 KiB3 images could be 74 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify CSS
18 KiB18 KiB could be saved by minifying CSS.
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.
3 checks passed
Mobile performance score: 90
90/100Your mobile performance score is 90. That is in Google's “good” band (90 and up).
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 755 ms of it running JavaScript. That is comfortably low.
Server response: 10 ms
10 msYour server sent the HTML in 10 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.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
9 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 472 ms
472 msReal visitors wait 472 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 27% faster for real visitors
-27%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 310 ms to 225 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.2 s
2.2 sYour largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Smartling's leading AI translation solution, paired with ex…”.
Total Blocking Time: 142 ms
142 msScripts block the page for only 142 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.4 g of CO₂ per visit
0.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 43.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.3 MB in 119 requests
1.3 MBYour homepage downloads 1.3 MB in 119 requests on a phone: scripts 528 KiB (31), fonts 288 KiB (7) and images 268 KiB (40). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 92 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (76 characters)
Your title is 76 characters, so Google will cut it off around 60: “Smartling | End-to-end localization & translation services for global growth”.
84 internal links, 27 external
The homepage links to 84 pages on smartling.com and 27 external pages.
7 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “Smartling connects your brand with customers around the globe. Translate, automate & manage your content across platfor…”.
One H1 headline
Your main headline reads: “Translate for every market, automatically”.
Canonical URL set
The canonical URL is https://www.smartling.com/.
Structured data in place
Structured data found: FAQPage.
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.smartling.com/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,904 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (8 KiB, 61 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
/-ab-variant-f8544d11-b79b-450b-b46a-f5e8784fca27 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and /-ab-variant-f8544d11-b79b-450b-b46a-f5e8784fca27 all use the title “Smartling | End-to-end localization & translation services for global…”. Search engines can't tell which page to show for a search, so each competes with the others.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken external link
1 link to other sites is dead, for example https://dashboard.smartling.com/ (404).
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
1 link through redirect chains
1 link go through two or more redirects, for example https://cta-service-cms2.hubspot.com/web-interactives/public/v1/track/click?encryptedPayload=AVxigLIxekHAVYLchZ0B2odI78wgBfyXp3sGJejt0g3ZaP0ZWX6HdGGEndR15N8jKhIjMNHNhz%2BVxUHetWH2mxjJtQBT%2BQM6aF2s0WnVHrfh4FSSIFoJkSc%2FL%2FCisM%2FVsWdGUiI4XqYbw9Du5ZV93LsfWZQUHOlTkFA9T2PQpGpEkVKwNfAKkjL4OvMdgtJ4QA%3D%3D&portalId=40052555.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
6 checks passed
Served over HTTPS
The homepage is served over HTTPS (smartling.com).
Valid certificate (34 days left)
The certificate from Google Trust Services · WE1 verifies for smartling.com and is valid for another 34 days.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://smartling.com redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
Domain and trust
No CAA record
smartling.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
smartling.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 17 years old
17 yearssmartling.com was registered in Sep 2009 through Amazon Registrar, Inc.. An established domain carries more trust with email providers and search engines.
Registered until Sep 2027
smartling.com is registered until Sep 2027.
Content and conversion
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.
About 1,175 words of copy
The homepage carries about 1,175 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Watch a demo”.
8 calls to action
The homepage has 8 calls to action, for example “Book a meeting”, “Watch a demo” and “Try for free”.
Social proof on the page
Social proof on the homepage: 15 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and HubSpot.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Email authentication
Email authentication score: 95/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:mail.zendesk.com include:40052555.spf07.hubspotemail.net ip4:50.18.195.33/32 ip4…”.
DKIM signing found
A DKIM key is published (selector “google”, “k1” and “s1”), so receivers can verify mail really came from you.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
25 other companies contacted
Loading the homepage contacts 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
Upkeep, stack and company
- It loads jQuery 1.7.1, older than 3.5 (which fixed known security holes).
Stack
- CMS
- HubSpot
- Framework
- jQuery
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- HubSpot
Hiring
- Hiring
- 9 open roles
- Teams
- Professional Services (3), Sales Development (2), All (1), Customer Success (1)
- Job board
- greenhouse
- Careers page
- www.smartling.com/careers (opens in a new tab)
Company
- Founded
- 2009
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on smartling.com, including 10 speed issues, 1 SEO issue 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.