Skip to main content
New Idea

SEO Improvement on Profile Images

  • October 28, 2021
  • 2 replies
  • 143 views

Suvi Lehtovaara
Forum|alt.badge.img

We’ve had an SEO audit done on our community. There are a number of improvements we’ll present here as ideas. The first one is about profile images in the community :relaxed::camera_with_flash:

We propose loading images as 40 * 40, only showing them 200 * 200 when needed.

Alternatively, we propose adding support for src-sets so that we can load the right image size for the right viewport. This would free up some network load without impacting visual quality.

2 replies

  • Contributor ⭐️⭐️
  • November 3, 2021

We noticed this when doing a traffic analysis, intrinsic size of assets versus the rendered size can be off by quite a bit, e.g. the loading a 200px (max) image for a 40x40 avatar. On limited connection, these kind of small issues tend to compound pretty fast. From the SEO side, with Web Vitals becoming an official ranking signal any network load you can shed is a plus. 

Ideally, in order to preserve quality through src-set, but for a quick solution dropping the intrinsic size to match the maximum size of the image rendered in the largest possible viewport (which from what we've seen, 60px) would already be a win.


Suvi Lehtovaara
Forum|alt.badge.img
  • Author
  • Helper ⭐️⭐️
  • February 9, 2023

We very much hope that this idea would get picked up, so we decided to enrich our original idea a bit.

SEO nowadays is all about the Web Vitals scores. On Insided's communities they seem to be pretty solid, but one of the main blocking factors we've seen has been the LCP* score, which is sitting just north of the "good" cutoff of 2.5s on mobile.

One avenue to improving the LCP is reducing the overall load on the page by using device appropriate responsive images. That means that for mobile devices we generally load smaller images in order to fit the viewport better.

*) 
Largest Contentful Paint or LCP, which marks the point in the page load timeline when the page's main content has likely loaded.