You are browsing:

Development Hot Tips

Landing Page lessons related to the development process. When you are further with your build, kick off the Landing Page Development Checklist.

Trim the fat

Hot Tip #61 is to trim the <head> fat.

Start by opening up your Landing Page source code view. In Google Chrome: File > View > Developer > View Source. Other browsers will be similar.

Copy all of the code between the opening and closing <head> tag and paste it into a text editor.

Use this checklist, starting from the top:

This can (and will) uncover scripts, font weights, and code snippets that add nothing but load time to your visitor’s experience.

As tedious as it sounds, your future Landing Pages will benefit from knowing what is behind them.

Include an email within error messages

Hot Tip #62 is to include a support email address within your error messages.

If your Landing Page payment integration offers message customization, include a support email address for when a problem persists:

🚫

✅

This can potentially convert dozens of disgruntled visitors into happy customers.

Hot Tip #64 is to delay your chatbot.

If you feel your Landing Page benefits from one, only kick that bugger off once your visitor has scrolled to the pricing table, FAQs, or footer.

A corner chat notification on arrival wrecks concentration, and we can’t afford to distract visitors while they decipher what we do.

Hot Tip #66 is to open non-essential links in a new tab.

Set links to documentation, support, privacy, and demos to open a new browser tab, keeping the primary Landing Page within a tab’s reach.

Or Don’t – A strong Counterargument by Jesse including several use-cases and additional UX reads. Always healthy to question UX decisions. I still vote for opening demos, support portals and blogs in new tabs – all 3 in my experience offer poor navigations to return to the primary page.

The end.

There are no more Hot Tips to load in this archive.