gettickr
Home
Features
PricingHelp
Getting Started
What is gettickr.app?
Free vs. Premium
Create Account
Timer Configuration
Create Countdown (Duration)
Create CountTo (Date)
Customize Design
Preview vs. Renderer
Save & Manage Timers
Remote Control
Streaming Integration
Streaming Platforms Overview
OBS Studio Integration
Streamlabs Integration
XSplit Integration
Website Integration
Website Integration Overview
iFrame Integration
WordPress Integration
Shopify Integration
Wix / Squarespace
Custom HTML Websites
Advanced Features
Timer State & Persistence
Free vs. Premium Timers
FAQ & Troubleshooting
Common Questions
Known Issues
Contact Support
Help Center
/
Website Integration
/
iFrame Integration

Table of Contents

What is an iFrame?Basic iFrame Code StructureCreating Your iFrame CodeSecurity ConsiderationsPerformance OptimizationTroubleshootingNext Steps

iFrame Integration

Information
iFrames are the universal method for embedding gettickr.app timers on any website. This guide shows you everything you need to know to implement timers using iFrame code.

iFrames are the fundamental technology behind embedding gettickr.app timers on websites. Understanding how to work with iFrames gives you the flexibility to integrate timers into any website platform or custom-coded page.

What is an iFrame?

An iFrame (inline frame) is an HTML element that embeds another HTML page within your current page. When you use an iFrame to embed a timer, you're creating a window on your webpage that displays your timer from gettickr.app.

AspectDescription
TechnologyStandard HTML element (<iframe>)
Browser SupportAll modern browsers (Chrome, Firefox, Safari, Edge)
CompatibilityWorks on all website platforms
ComplexitySimple - just paste HTML code
FlexibilityFull control over size, position, and styling
Tip
iFrames are the same technology used to embed YouTube videos, Google Maps, and other external content on websites. If your platform supports those, it supports gettickr.app timers!

Basic iFrame Code Structure

The basic iFrame code for embedding a timer follows a simple HTML structure:

<iframe
  src="https://gettickr.app/r/#YOUR-TIMER-ID"
  width="800"
  height="400"
  frameborder="0"
  allowfullscreen
>
</iframe>

iFrame Attributes Explained

AttributePurposeExample ValueRequired
srcTimer URL to displayhttps://gettickr.app/r/#abc123✅ Yes
widthiFrame width800 (pixels) or 100% (responsive)✅ Yes
heightiFrame height400 (pixels)✅ Yes
frameborderBorder around iFrame0 (no border)⬜ Optional
allowfullscreenEnable fullscreen capabilityNo value needed⬜ Optional
loadingWhen to load iFramelazy (load when visible)⬜ Optional
titleAccessibility description"Countdown Timer"⬜ Recommended
Tip
Always include a title attribute for accessibility - it helps screen readers describe the content to visually impaired users.

Creating Your iFrame Code

Follow these steps to create iFrame code for your timer:

Step 1: Get Your Timer URL

  1. Create and customize your timer in the Editor
  2. In the Renderer section, find your timer's display URL
  3. Copy the complete URL (looks like https://gettickr.app/r/#YOUR-TIMER-ID)

Step 2: Choose Your Dimensions

Decide on the width and height based on your timer's design and where it will appear:

Timer PlacementRecommended WidthRecommended HeightAspect Ratio
Full-width100%400-600px~16:9 or 16:6
Hero Section1200px or 100%600px2:1
Sidebar300-400px200-300px~4:3
Content Width800px400px2:1
Small Widget400px200px2:1
Information
Match the iFrame dimensions to the design dimensions you set when creating your timer in the editor for the best appearance.

Step 3: Build Your Code

Replace YOUR-TIMER-ID with your actual timer ID from the URL:

<iframe
  src="https://gettickr.app/r/#YOUR-TIMER-ID"
  width="800"
  height="400"
  frameborder="0"
  title="Countdown Timer"
  allowfullscreen
>
</iframe>

Step 4: Add to Your Website

Copy the complete iFrame code and paste it into your website:

  • HTML/Code Editor: Paste directly into your HTML
  • Website Builder: Use "Custom HTML" or "Embed Code" block
  • CMS: Add to HTML block, custom HTML widget, or text editor (HTML mode)
Warning
Make sure to paste the code in HTML mode, not visual/rich text mode. If you paste in visual mode, the code will appear as text instead of rendering the timer.

Security Considerations

Modern browsers implement security features for iFrames to protect users:

Security FeatureWhat It Doesgettickr.app Compatibility
HTTPS RequirementMany sites only allow HTTPS iFrames✅ gettickr.app uses HTTPS
X-Frame-OptionsControls who can embed the content✅ Allows embedding
CSP HeadersContent Security Policy restrictions✅ Whitelisted
Sandbox AttributeRestricts iFrame capabilities⬜ Not needed for timers
Information
Gettickr.app timers are designed to work safely in iFrames without requiring special security configurations. Default browser security settings work perfectly fine.

Optional Sandbox Attribute

If your website security policy requires it, you can add sandbox restrictions:

<iframe
  src="https://gettickr.app/r/#YOUR-TIMER-ID"
  width="800"
  height="400"
  sandbox="allow-scripts allow-same-origin"
  style="border: none;"
>
</iframe>
Warning
Only add sandbox attribute if specifically required by your security policy. It can restrict timer functionality if not configured correctly.

Performance Optimization

Lazy Loading

Defer loading iFrames until they're near the viewport:

<iframe
  src="https://gettickr.app/r/#YOUR-TIMER-ID"
  width="800"
  height="400"
  loading="lazy"
  style="border: none;"
>
</iframe>

Benefits:

  • Faster initial page load
  • Reduced bandwidth for users who don't scroll to timer
  • Better performance on mobile devices
Tip
Use loading="lazy" for timers that appear below the fold (not immediately visible when page loads).

Performance Best Practices

PracticeWhyHow
Single Timer Per PageMinimize resource usageUse one timer, not multiples
Appropriate SizeDon't load huge iFrames unnecessarilyMatch design dimensions
Lazy LoadingLoad only when neededAdd loading="lazy"
Avoid Nested iFramesComplexity hurts performanceOne level only

Troubleshooting

Timer Not Appearing

ProblemSolution
Blank space where timer should beVerify timer URL is correct
No iFrame visible at allCheck HTML mode (not visual editor)
Error message in iFrameTimer may have been deleted or URL is incorrect
Black screeniFrame dimensions may be incorrect
Tip
Open the timer URL directly in a browser to verify it works before troubleshooting the iFrame embedding.

Sizing Issues

ProblemSolution
Timer appears too smallIncrease width and height values
Timer appears cut offCheck iFrame dimensions match timer design
Timer overflows containerAdd max-width: 100% to iFrame
Unwanted scrollbarsSet scrolling="no" or overflow: hidden
Wrong aspect ratio on mobileImplement responsive aspect ratio container

Platform-Specific Issues

PlatformCommon IssueSolution
WordPressVisual editor strips codeUse Code Editor or HTML block
WixiFrame not allowed in textUse HTML iFrame element from Add menu
SquarespaceLimited iFrame supportUse Code Block, not Text Block
ShopifyiFrame in liquid templatesUse proper Liquid syntax for HTML
WebflowEmbed element neededUse Embed element, not HTML Embed
Warning
Some website platforms filter or restrict iFrame code for security. If your iFrame doesn't work, check your platform's documentation about embedding external content.

Browser Console Errors

Check browser developer console (F12) for error messages:

X-Frame-Options denied

Solution: Contact your website host - your site may be blocking iFrames.

Mixed Content: blocked loading insecure content

Solution: Ensure timer URL uses https:// not http://

CSP: frame-src violation

Solution: Update your Content Security Policy to allow gettickr.app

Next Steps

  • WordPress Integration - Platform-specific guide for WordPress
  • Shopify Integration - E-commerce timer setup
  • Custom HTML Integration - Advanced implementation techniques
  • Customize Timer Design - Make your timer match your website aesthetic
Tip
For platform-specific instructions beyond basic iFrame code, check out the dedicated integration guides for your website platform!
2026|Made by
ChangelogLegal NoticePrivacy PolicyCookie PolicyTerms