layer5 icon indicating copy to clipboard operation
layer5 copied to clipboard

Improve Site Speed: Implement suggestions from Pingdom Website Speed Test

Open leecalcote opened this issue 4 years ago • 19 comments

Current Behavior The Pingdom Website Speed Test of layer5.io currently receives a low score. Suggestions are made in the test as to how to speed up the layer5.io site.

Desired Situation Implement the suggestions and improve the site speed and speed score.


Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

leecalcote avatar Nov 26 '21 13:11 leecalcote

Hello, @leecalcote. I saw the website speed test score, and yeah, it is not that great.

To fix this, we can add .htaccess for caching purposes, resolving the first issue of Add expire header. But it will be great if you do it or assign this task to someone who has worked on this website. Cause if anything gets messed up, then the whole website will face issues.

Since I am new to this project, I don't have that much information; otherwise, I would have done that. :)

For the optimization part, I can convert images to webp, which will significantly help the site perform better. If it is okay for you, then you can assign this task to me.

Also, I have one more suggestion to add lazy loading and gatsby-images. It will also help the make the website quite fast.

sahilsuman933 avatar Nov 27 '21 17:11 sahilsuman933

@sahilsuman933, we don't use Apache as a web server, but use GitHub Pages.

leecalcote avatar Nov 27 '21 17:11 leecalcote

Okay Sir!

sahilsuman933 avatar Nov 27 '21 17:11 sahilsuman933

Can I go ahead with optimizing the images for the site?? Using Gatsby to convert it to webp as it default on supported browsers and a fall back to jpg on unsupported ones.

kayceeDev avatar Dec 16 '21 22:12 kayceeDev

@kayceeDev, yes, that sounds great.

leecalcote avatar Dec 16 '21 22:12 leecalcote

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jan 31 '22 00:01 stale[bot]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

stale[bot] avatar Feb 03 '22 03:02 stale[bot]

@Nikhil-Ladha, do you think that we need to breakout individual tasks here?

leecalcote avatar Feb 03 '22 04:02 leecalcote

Good question. Maybe or maybe not, considering we already have another issue #2172 which tracks the performance of the site this might not be required. But, since this issue tracks a completely different tool I think we are good to keep this issue open and make the enhancements suggested by it. I see the score is much better now at 81, but a few more enhancements could be made and some of them are similar to lighthouse.

Nikhil-Ladha avatar Feb 03 '22 05:02 Nikhil-Ladha

Hi, I am Aaditya Singh, a contributor to OpenForce 2022. I would like to work on this issue. I would be making a PR as soon as I am done with resolving the issue. Thank you

Aaditya-Singh78 avatar Mar 10 '22 09:03 Aaditya-Singh78

@Aaditya-Singh78 That's great. There are so many issues pointed out by the Analyzer. You can go ahead and choose any of them to work on. But first, go through the open pull requests and see if any of these suggestions by the analyzer have been currently worked on before picking an issue. Feel free to ask any question on the slack channel if you need clarifications.

kayceeDev avatar Mar 10 '22 09:03 kayceeDev

@Nikhil-Ladha @kayceeDev is this issue been worked upon? I'm a contributor at Open-Force.

soumya-dash3 avatar Mar 15 '22 05:03 soumya-dash3

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Apr 29 '22 09:04 stale[bot]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

stale[bot] avatar May 01 '22 14:05 stale[bot]

@sahilsuman933 we're still doing poorly on performance. See this web.dev performance report - https://web.dev/measure/?gclid=Cj0KCQjwxIOXBhCrARIsAL1QFCZ_abOHFnIqOpNgeY0S8fmG8G1iKX1wW2F0-UR8RL5L9BM6JtkReuwaAuXmEALw_wcB&url=https%3A%2F%2Flayer5.io

Will you look at actions that can be taken to improve speed?

leecalcote avatar Jul 28 '22 03:07 leecalcote

@adithyaakrishna

leecalcote avatar Jul 28 '22 04:07 leecalcote

@leecalcote Sure.

sahilsuman933 avatar Jul 28 '22 05:07 sahilsuman933

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Sep 20 '22 17:09 stale[bot]

Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a MeshMate or any other community member for assistance.


        Be sure to join the community, if you haven't yet and please leave a :star: star on the project :smile:

github-actions[bot] avatar Sep 20 '22 18:09 github-actions[bot]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Nov 12 '22 14:11 stale[bot]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

stale[bot] avatar Dec 16 '22 05:12 stale[bot]