1C-Bitrix for Photographers: Portfolio, Booking, Client Cabinet

A photographer uploads 4K images — visitors complain about slow loading. A gallery of 30 photos weighs 150 MB and takes 15 seconds to load. The result — losing clients. Our company — 10+ years of certified experience in 1C-Bitrix development, over 50 projects for photographers — guarantees: even dozens of galleries do not affect speed. Development on 1C-Bitrix allows packaging visuals into WebP, setting up CDN, and giving clients a personal cabinet for downloading. Contact us for a guaranteed consultation — we will show case studies. Most projects start from $2,500 and save up to 30% compared to custom alternatives.

Why 1C-Bitrix is chosen for a photographer's website?

The platform provides ready-made modules for information blocks, tagged caching, and background agents. For portfolios, information blocks v2.0 with multiple file properties are used. Booking, personal cabinet, and blog are covered by standard tools. The built-in SEO module generates sitemap and Schema.org markup automatically. According to Bitrix documentation, component 2.0 and ORM ensure high performance even under thousands of requests.

How to optimize a portfolio for fast loading?

The portfolio is the core of the site. A photographer uploads images 4000–6000 px, 5–15 MB each. The visitor should see the gallery instantly.

Step 1: Information block structure

• Sections: genres (wedding, reportage, product, portrait).
• Elements: photo shoots or series.
• Properties: description, date, location, multiple file property "Photos".

Step 2: Thumbnail generation

After uploading a photo, the handler OnAfterIBlockElementUpdate launches a background task via event manager. Agents are used. Set of thumbnails:

The original is saved but not served directly — only via thumbnails. CFile::ResizeImageGet() with proportional resize maintains proportions. WebP is converted via Imagick, support check via Accept header or <picture> tag. WebP is 2–3 times lighter than JPEG at the same quality.

Step 3: Lazy loading with progressive display

Standard loading="lazy" causes layout shift. Our solution:

1. Placeholder with dominant color — upon photo upload, the average color is extracted (PHP), saved as an element property. In CSS, the placeholder is colored with that color.
2. Blur-up — micro-preview 20×13 px (< 1 KB) is inlined into HTML as base64, displayed blurred. When the real image loads — smooth replacement via CSS transition.
3. Intersection Observer — custom script loads images when approaching viewport (margin 200px). This speeds up visible image loading by 2 times compared to simple loading=lazy. Our lazy loading method is 2x faster and reduces layout shifts.

The gallery grid — Masonry on CSS Grid: grid-template-columns: repeat(auto-fill, minmax(300px, 1fr)). Lightbox — Fancybox 5 or GLightbox with swipe support.

Step 4: CDN connection

For audiences from different regions, CDN is mandatory. Configuration via the Bitrix CDN module or manual nginx setup with proxying to CloudFlare / BunnyCDN. Thumbnails are served via CDN, originals from the server directly. CDN reduces loading time by 40-60% compared to no CDN.

Protection from downloading

Cannot be fully prevented, but can be complicated:

• Disable context menu (JavaScript).
• Watermark on displayed versions.
• Serve via CSS background-image instead of <img>.

Result: a gallery of 30 photos loads in 1.5–2 seconds on mobile LTE. The first screen is displayed in 0.8–1 second thanks to inline placeholder and preload hero image.

How is the booking system structured?

Booking — via an interactive calendar of availability. The client sees free dates and submits a request.

Implementation: an information block "Schedule" with elements as days. Properties: date, status (free/occupied/pre-booked), shoot type. The frontend renders a monthly grid, occupied days are gray. Data is loaded via AJAX when changing the month.

The client clicks a free date → form: name, phone, shoot type, location, comment. The request creates a lead in CRM or sends an email. After confirmation, the photographer changes the day status to "occupied" via the admin panel.

Services with packages

Information block "Services": name, format (hourly/package), duration, what's included, number of photos, link to gallery. On the frontend — cards with a "Book now" button.

Blog and SEO

The blog attracts traffic via queries like "how to prepare for a wedding photo shoot" and demonstrates expertise. Implemented via a standard news information block. SEO: SEF through urlrewrite, meta tags via information block properties, breadcrumbs, Schema.org Article in JSON-LD. Sitemap generated by the SEO module. Our proven SEO approach guarantees better rankings.

Client cabinet for delivering photos

Instead of Yandex.Disk — a closed gallery on the site. Information block "Client galleries": link to user, shoot date, set of photos, status, access period. Access: authorization or password-protected link. Gallery with lightbox, download individual photos or ZIP archive via ZipArchive. Watermark on previews — via GD/Imagick. This reliable system ensures secure photo delivery.

What's included in the work and timelines

• Analysis and prototyping of portfolio, services, calendar structure.
• Design mockup with focus on mobile version.
• Setting up information blocks, thumbnail generation, caching.
• Developing client cabinet with authorization and online booking.
• Integrating CDN, optimizing Core Web Vitals.
• Delivering documentation, training, post-launch support.

Total: 7–9 weeks. It is critical to receive photo materials in advance — processing and uploading take more time. Pricing is discussed individually, starting from $2,500.

Get a certified engineer consultation: contact us to discuss your project. We will offer the optimal solution for your tasks.