• site home
  • blog home
  • galleries
  • contact
  • underwater
  • the bleeding edge

the last word

Photography meets digital computer technology. Photography wins -- most of the time.

You are here: Home / The Last Word / Speeding up a web site

Speeding up a web site

April 2, 2018 JimK 1 Comment

This begins another series of posts on my experiences in optimizing my web gallery and blog presence. Like the last set of posts I did on this subject, it could just as well be posted on The Bleeding Edge, but, since I figure that my struggles with this issue will be useful to most photographers with an on-line presence not based on social media, I’m going to post it here.

About 18 months ago, I converted my galleries from a plain-old-CSS to WordPress. That went pretty well. About six months ago, Google started flagging sites that don’t use secure sockets layer (SSL) in ways that went beyond the absence of the green padlock. Some of the warnings are now pretty scary. Google wants all web page addresses to start with “https://,” and they’re tightening the screws to bend the ‘net to their will. I sympathize, and know that the right thing would have been for me to switch to SSL even without their prodding, but I guess I was just lazy. A month or so ago I moved both The Bleeding Edge and this blog over to SSL. Things appeared to work fine, except that the pictures didn’t load as fast as they used to. I also changed the main site, where the galleries are, and found the performance unacceptable, so I switched it back.

I don’t know why SSL slows things down, and I don’t have the server-side expertise to find out. So I started exploring other options. It’s taken a while, but the three I’ve worked on the most are:

  • A non-WordPress, hosted package from Squarespace.
  • Managed WordPress from Media Temple, my current hosting supplier.
  • Adding a content-distribution network (CDN) to my existing WordPress sites.

I happened upon Squarespace because I have a friend who converted a CSS-based photography web site to their offering. What you get from Squarespace:

  • A graphical user interface for creating content
  • A set of pretty templates
  • A hosting platform
  • Use of their SSL certificates and services
  • Security and backup services
  • Analytics
  • Features that make it easy to set up a store
  • Access to their CDN

Does that sound good to you? Great. Don’t want all that? Tough. Want to mix-and-match with your own pieces? Forget it.

The good news:

  • It’s dirt cheap: 18 bucks a month for the whole ball of wax.
  • It’s fast.
  • They do the staging of images in multiple resolutions for you.
  • The highest resolution they recommend is 2K on the long side, and sites with images that big still load fast.
  • The GUI is reasonably well thought-out.

The bad news:

  • The templates don’t work like WordPress templates. Each template has a set of features, and if you want some feature that isn’t in the template, you switch to another template.
  • There are caching issues with the GUI. Sometimes, you can make changes, and they won’t take. But the next day, when you go back to the site, there they or. Or not, seemingly randomly.
  • There’s no off-line GUI, just a browser-based one. So site development takes place at web speeds. Sloooow.
  • When you switch templates, your content becomes unlinked, and you must build your website manually all over again.
  • There is no programmatic interface, and thus no way to automate bulk changes. You have to laboriously drag and drop your way into making them.
  • You can’t clone a site. That means that, if you want to roll out a big change, you need to set up a new site, manually recreate your original site, make the changes, test, change the DNS entries, let them propagate, then take down the original site.
  • As far as your content is concerned, SquareSpace is a bit like the Hotel California. You can put in all the data you want, and you can get much of it back in XML, but you can’t then import that to copy content to another Squarespace site, or to move that content to a WordPress site.

My take is that, although unashamedly proprietary, for some users Squarespace is just about perfect. But not for me. It just doesn’t seem like it has the tools that serious web developers expect.

Next: the two WordPress options.

 

 

 

 

The Last Word

← Siri and the iPhone camera Sony a9 has an AA filter →

Comments

  1. Luis says

    April 5, 2018 at 11:10 am

    Just in case you didn’t know, CDN for images could be done with just a few clicks using Jetpack, the service is called “photon” and is free.
    I use managed service in one of my sites hosted in Dream Host (it is called dreampress). It work really fast since they add Varnish cache.

    Btw your site loads fast from spain 😉

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

June 2025
S M T W T F S
1234567
891011121314
15161718192021
22232425262728
2930  
« May    

Articles

  • About
    • Patents and papers about color
    • Who am I?
  • How to…
    • Backing up photographic images
    • How to change email providers
    • How to shoot slanted edge images for me
  • Lens screening testing
    • Equipment and Software
    • Examples
      • Bad and OK 200-600 at 600
      • Excellent 180-400 zoom
      • Fair 14-30mm zoom
      • Good 100-200 mm MF zoom
      • Good 100-400 zoom
      • Good 100mm lens on P1 P45+
      • Good 120mm MF lens
      • Good 18mm FF lens
      • Good 24-105 mm FF lens
      • Good 24-70 FF zoom
      • Good 35 mm FF lens
      • Good 35-70 MF lens
      • Good 60 mm lens on IQ3-100
      • Good 63 mm MF lens
      • Good 65 mm FF lens
      • Good 85 mm FF lens
      • Good and bad 25mm FF lenses
      • Good zoom at 24 mm
      • Marginal 18mm lens
      • Marginal 35mm FF lens
      • Mildly problematic 55 mm FF lens
      • OK 16-35mm zoom
      • OK 60mm lens on P1 P45+
      • OK Sony 600mm f/4
      • Pretty good 16-35 FF zoom
      • Pretty good 90mm FF lens
      • Problematic 400 mm FF lens
      • Tilted 20 mm f/1.8 FF lens
      • Tilted 30 mm MF lens
      • Tilted 50 mm FF lens
      • Two 15mm FF lenses
    • Found a problem – now what?
    • Goals for this test
    • Minimum target distances
      • MFT
      • APS-C
      • Full frame
      • Small medium format
    • Printable Siemens Star targets
    • Target size on sensor
      • MFT
      • APS-C
      • Full frame
      • Small medium format
    • Test instructions — postproduction
    • Test instructions — reading the images
    • Test instructions – capture
    • Theory of the test
    • What’s wrong with conventional lens screening?
  • Previsualization heresy
  • Privacy Policy
  • Recommended photographic web sites
  • Using in-camera histograms for ETTR
    • Acknowledgments
    • Why ETTR?
    • Normal in-camera histograms
    • Image processing for in-camera histograms
    • Making the in-camera histogram closely represent the raw histogram
    • Shortcuts to UniWB
    • Preparing for monitor-based UniWB
    • A one-step UniWB procedure
    • The math behind the one-step method
    • Iteration using Newton’s Method

Category List

Recent Comments

  • JimK on A Modest Proposal
  • Brandon on A Modest Proposal
  • DC Wedding Photographer on Price and Performance: Hasselblad X vs. Fujifilm GFX
  • DC wedding photographer on A Modest Proposal
  • NiceDays on Do Raw Developers Use the Embedded JPEG as a Color Reference?
  • Christer Almqvist on Diffraction and the Airy disk diameter
  • Paul R on Price and Performance: Hasselblad X vs. Fujifilm GFX
  • JimK on Do Raw Developers Use the Embedded JPEG as a Color Reference?
  • Jack Hogan on Diffraction and the Airy disk diameter
  • Jack Hogan on Do Raw Developers Use the Embedded JPEG as a Color Reference?

Archives

Copyright © 2025 · Daily Dish Pro On Genesis Framework · WordPress · Log in

Unless otherwise noted, all images copyright Jim Kasson.