10007791ACTIVETime to load: 1.0 seconds
| Date checked | CO2 / grams | Page size | Energy |
|---|---|---|---|
| 2023-12-07 | 1.65 | 6.5MB | GRID? |
| 2022-09-06 | 6.07 | 10.1MB | GRID? |
| 2022-06-09 | 3.83 | 6.4MB | GRID? |
| 2022-04-12 | 3.77 | 6.3MB | GRID? |
| 2022-02-01 | 6.38 | 10.6MB | GRID? |
| 2021-11-03 | 3.70 | 6.1MB | GRID? |
| 2021-10-06 | 3.79 | 6.3MB | GRID? |
| 2021-09-01 | 3.72 | 6.2MB | GRID? |
| 2021-07-29 | 6.31 | 10.5MB | GRID? |
| 2021-06-30 | 3.71 | 6.1MB | GRID? |
| 2021-06-01 | 3.70 | 6.1MB | GRID? |
First, check that images are appropriately sized - you most likely don't need a 6000x4000 pixel image straight from a digital camera. In Windows, the Photos software will let you quickly shrink huge images and will give you an improvement.
Next you could try using tinyjpg.com (JPG image) or tinypng.com (PNG image) to further optimise your image. This will strip out metadata that may be taking up lots of space.
*This is an estimate from Google PageSpeed and you may get much better results than this in practice.
Aside from images, here are the biggest resources:
Here are the largest sources of third-party code:
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading.
If you use the Twitter widget to load a timeline it may be loading as many as 100 of your recent tweets which may contain lots of images. Try setting 'data-tweet-limit' to the most recent 3.
