TeleportHQ test data

The cafe brief was pasted word for word into the 'Business description' box. The AI then showed three screens (design preferences, colours and fonts, and a build screen) and I accepted what it had picked. The clock ran from pressing Enter to the home page showing in the editor, and then to the published address.

The cafe home page was on screen in the editor after about 4 minutes, and the Publish button put it on a web address in about 30 seconds. The AI had planned five pages and built two: the home page and a Terms page. Menu Item Details and Catering waited under 'Planned, not built' with a Create button. Each Create took about a minute and used about 2,500 tokens. Menu, About and Contact were never planned, and the site's own menu links to them.

The live address is a password page. The Publish panel says 'Visitors must enter a password to see your site, at every address it is published on.' The panel has no switch to turn it off. TeleportHQ's help centre says that on the trial the password is added by TeleportHQ when you publish and stays until the workspace subscribes.

The panel shows an address ending in .teleporthq.site, which answers 404 on Vercel. The site really lives at an address ending in .teleporthq.app, which the pop-up gives after the publish.

The trial's pop-up says 'All deployments and custom domains will be removed. All projects will be archived: no actions can be taken on them.' when the 7 days end.

• Only one of the three briefs could be built (one project on the plan), so no median was possible. The times are from my notes of that one run.

The five pages of the cafe site were opened at 360, 768 and 1440 pixels wide through the password page. A checker counted contrast faults (axe-core 4.10), tap targets under 24 pixels, sideways scrolling and broken images. I also looked at the pages by eye on a phone-sized window.

The checker counted 12 faults on 5 pages: pale text that fails the contrast rule on all 5 pages (1 to 7 spots per page), tap targets under 24 pixels on all 5 pages (2 to 8 per page), and sideways scrolling at 360 pixels on the home and About pages. There were no broken images and no picture without alt text.

The home page's main headline, 'Handcrafted warmth, slow sourdough & our signature latte', is cream text on a cream background, and the hero image beside it is almost invisible. The result is a blank screen under the menu bar on desktop and on a phone. The About page, which the AI made later, has a readable headline.

The phone-only edit hid a small label above the headline at 390 pixels. A floating 'Built in TeleportHQ' badge sits at the bottom of every page; the pricing page lists removing it as a paid feature.

• Pages were checked through the password page with a cookie, on the live address. The tap-target and contrast counts follow the same rules as for the other builders. I did not run a keyboard walk.

The cafe's 20 facts were checked on the live pages: by a script that looks for each fact in the page text, then by hand. Anything the brief did not give was listed.

19 of the 20 cafe facts were on the live site: name, kind of business, owner, 2019, address, phone, email, both sets of opening hours, all five prices, the oat milk charge, free Wi-Fi, the dog-friendly patio, catering for 40 with 48 hours' notice, and Instagram. The 20th fact is the page list. The brief asked for Home, Menu, About, Catering and Contact with a contact form. The site has Home, About and Catering, a page about one drink that the Menu link opens, and a Terms page. There is no Contact page and no form.

The AI added no customer quotes, awards or staff names. It added small extras: 'Hawthorne District', 'Wrenfield Corridor', 'Southeast Portland', 'fresh water bowls, cool shade' and a 'Founding manifesto' heading.

The oat milk price ($0.75 extra) is on the Catering and drink pages and not on the home page.

• Only the cafe was built, because the plan allows one project. The check ran on the live pages after my edits, so the Catering text includes the shorter wording I asked for.

Each of the twelve business points was to be tried on the live cafe site. I opened the Publish panel, the Backups button and the settings screens, and read what each said.

The Publish panel offers 'Custom domain, TRIAL, 0 of 1 slots used', so one domain can be connected on the trial. I did not connect one: the site is removed on 4 November.

The cafe has no form, because the Contact page was never built, so no message, order, tax setting or mailbox could be tried. The cafe brief did not ask for a shop. The New Project screen offers E-commerce, Web App, Bookings and Blank types, and the plan allows one project, so I could not test a shop.

The Backups button is greyed. Its tooltip says 'Project backups aren't included in the trial. Subscribe to unlock.' The pricing page lists 'Automatic backups' for the free column, so the two disagree.

• No domain was connected, no form message was sent and no order was placed.

I opened the Code button, its Download tab and the pricing page, and read the help centre's export articles.

The Code tab says 'Your plan includes 10 code views.' The Download tab says 'Code downloads aren't included in your plan. Subscribe to a paid plan to export your project in HTML, CSS, Next.js, React, Vue or Angular.' It lists React, Next, Vue, Nuxt, Angular, HTML and UIDL, with 'Export to GitHub' and 'Download ZIP' buttons.

On the pricing page 'Code access & export' is shown as not included on the free column and included on Pro and Premium. The help centre says a trial can look at the code but not download it, and that web apps cannot be downloaded as code at all.

When the trial ends the site goes offline and the project is archived.

• A reviewer's Trustpilot post says the Next.js download did not run on a plain static host. I did not test that.

I read TeleportHQ's help centre for the three standard questions and for the password page, and sent one email to the address on the site.

The help centre has an article for each question. Connecting an outside domain: 'How to connect your own domain' (publish first, then Custom domain, Configure, then the DNS records to add). A form message that does not arrive: 'Why is my form not working?' (the site must be published on TeleportHQ hosting). Changing billing: 'How to switch between monthly and yearly billing' and 'My payment failed: how do I update my card?'. The password page: 'How to password-protect your site' explains that on the trial TeleportHQ adds the password itself.

I sent one email on 28 October 2026 to hello@teleporthq.io, the only address on the site, with the three questions and one about the password page. No reply had arrived when I wrote this. The editor also has a chat widget; I did not use it.

• I did not follow the billing steps because they need a paid plan.

The twelve fixed edits were done on the live cafe site. Almost all went through the AI assistant, which uses tokens. Each answer was checked on the live address after a republish. The assistant often asks to confirm a change or asks a question first.

8 of 12 edits worked. Done: move a section (second try; the first time it said the sections were already in that order), the site font (Montserrat, on the live site), a new About page with a menu link (about 3 minutes, 4,300 tokens; the link is also in the footer), a footer line, a button link, a replaced and centred image (the AI first asked which picture), a phone-only change (the label is hidden at 390 pixels and shown at 1440) and a shorter Catering headline and text.

Not done: the colour scheme (the warm yellow was applied, the navy was not: 'I couldn't complete it while preserving your existing text colours.'), a duplicated section (the AI said 'The duplication wasn't completed reliably' and the page then held three Catering blocks), embedded HTML (the AI added the block with an extra span inside it and said it could not keep my HTML exactly) and a new form field (the cafe has no form, because the Contact page was never built).

Time and tokens: a simple edit took 40 seconds to 1 minute and 500 to 1,300 tokens. The embed edit took about 3 minutes and 4,500 tokens. The trial gave 30,000 tokens once and 963 were left at the end. The editor's Project settings has a 'Custom code' box for the head and body of every page, which I did not try.

• Edits cost tokens and the meter shows only the total. The crop tool and the Custom code box were not tried. A second run of the misses was not possible once the tokens were nearly gone.

Lighthouse 13.5 tested the home page and the Catering page of the live cafe site, three runs each with phone settings and three with desktop settings, with the computer otherwise idle. A cookie from the password page was passed so that Lighthouse saw the real pages.

The phone median is 72 out of 100 across six runs: the home page scored 72, 72 and 72, and the Catering page 73, 71 and 73. On desktop the home page scored 91, 92 and 91 and the Catering page 86, 86 and 85.

On phones the main picture took 7.6 seconds on the home page and 11.0 to 11.4 seconds on the Catering page, which weighs 4.8 MB against 2.1 MB for the home page. Nothing jumped around: layout shift was 0 on every run, and the time the page was blocked was 0 to 139 milliseconds.

• Two pages of one site, not six pages of three. The live address is behind a password page, which Lighthouse passed with a cookie, so a public site may differ slightly.

Each of the twelve points was read in the live page source and the files of the cafe site, and the settings screens were opened to see what can be edited.

10 of 12 points were seen on the live site: a title and a description on every page (descriptions 90 to 151 characters), one main heading per page, alt text on every picture (none missing), clean page addresses such as /about, an automatic sitemap.xml that lists the five pages, a robots.txt, a canonical tag, structured data (three or four blocks per page), and social-card tags (title and image).

The two points not seen live are 301 redirects and the per-page no-index. Both exist in the settings: each page has a 'No Index' box, a 'Custom Canonical' box and a 'Custom Redirect' box, and Project settings has 'Search engines: Title, description, sitemap, robots and redirects'. I did not set them and republish.

The Publish panel's own check says 'After publishing: 1 thing to check': one page (About) had no search title or description. The visitor's password page carries 'noindex, nofollow'; the pages themselves carry no robots tag.

• The live address is behind a password page, so Google could not index it as it stands. The checks are on the pages a visitor sees after the password.

I read the plans from TeleportHQ's pricing page, in both the monthly and the yearly view, and worked out the yearly cost of the cheapest plan that connects a custom domain and removes TeleportHQ's badge. I did not reach a checkout and paid nothing.

Pro is $14 a month on yearly billing, which is $168 a year, or $20.99 a month billed monthly, about $252 a year. Premium is $28 on yearly billing or $39.99 monthly. The page says 'SAVE 33%' for yearly billing.

The free column is a '7 Day Trial' at $0 with 1 website, 200 pages, 30,000 AI tokens once and 1 custom domain. 'Remove TeleportHQ Branding', 'Private Projects' and 'Code access & export' are not included. Pro adds unlimited websites and pages, 100,000 tokens a month, 2,000 form submissions a month and 10 GB of bandwidth; Premium adds web-app features and 150,000 tokens a month.

I could not read a renewal price, because I did not reach a checkout. The pricing page shows one price for each billing period.

• Read from the public pricing page and not from a checkout, because I may not enter a card. The renewal price, the payment methods and any extra fees were not seen.