2 main suggestions regarding Sparkle

I am using Sparkle since few monthes (very happy with) and I have 2 main remarks :

  1. It is too easy to destroy your work clicking on “destroy the article” : could you please add a alert message “do you really want to destroy your article?”

  2. could you open a large subject about Google Speed optimisation?

Thank you!

1 Like

Hi @Angel49,

  1. thanks for the suggestion
  2. this is a more complex issue to discuss:

We dogfood our own app, so we use the homepage as a test of our development on Sparkle 3. In this particular instance I had turned off webp image generation, which is one thing pagespeed is complaining about. I just added webp generation again and there’s essentially no difference in pagespeed.

The “speed index” is biased by Google testing from the US and our site being hosted by DigitalOcean in Amsterdam. Yes this is a real problem, but not a Sparkle problem per se. We don’t currently have a solution for this, if this were your site you might solve it by placing a CDN in front of your Sparkle site (say cloudflare).

The LCP metric is new, public as of last week, and we’re still trying to figure out how to address it. I think we’re doing good, a lot of the weight in the LCP is again the download performance for assets (so the aforementioned testing from a different region). There’s a chrome web vitals plugin and a LCP indicator in the performance section of the web dev tools, and they both show the site doing good.


Thank you for the answer.

Just to follow up on this, pagespeed is a terrible benchmark of performance. I removed the fade-in of a couple elements at the top of the page, and the pagespeed score jumped up. Too bad pagespeed is all we have.

It’s owned and used by Google : so, good or not, it’s like God’s voice.