extensions
extensions copied to clipboard
raycast
Add pagespeed extension
Description
A simple Raycast extension that monitors PageSpeed insights for websites based on page-speed.dev.
Screencast
https://github.com/raycast/extensions/assets/1022166/153d9d68-440a-4970-894c-02ed18db5c09
Checklist
- [x] I read the extension guidelines
- [x] I read the documentation about publishing
- [x] I ran
npm run buildand tested this distribution build in Raycast - [x] I checked that files in the
assetsfolder are used by the extension itself - [x] I checked that assets used by the
READMEare placed outside of themetadatafolder
Congratulations on your new Raycast extension! :rocket:
We're currently experiencing high demand and limited capacity. As a result, extension reviews might take longer than usual to get the initial review. Please expect an initial review within 5-10 business days.
Once the PR is approved and merged, the extension will be available on our Store.
Sorry for the inconvenience
Hi @pernielsentikaer, thanks a lot for the feedback. I can make the change really easily, if you think that's the best way to go I'll can do so, just let me know.
If you want to keep it in one view, then you could do something like how this extension is doing it by using a List.EmptyView to add it
What do you think of that (or the previous mentioned)
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
Hello @pernielsentikaer apologies for the super late reply, it has been a hectic period.
I took some time and refactored the application to match the UX standards you've mentioned.
Used a <Form /> component with individual submissions and a proper listing view.
Let me know your thoughts or considerations.
I keep getting this error in the latest update, do you have an idea why?
Hello @pernielsentikaer for some reason the API is failing to parse the results for this specific domain, https://page-speed.dev/dr.dk
I am sure @danielroe can give you more insights, but the extension is properly fetching the results, it also works with short but valid domains. My gut feeling says that they might be restrictions from the domain owner blocking crawling requests.
The issue is that there is a redirect in place from dr.dk -> www.dr.dk. We have an open PR to handle redirects so this should be resolved shortly.
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
Hey @danielroe I can't quickly patch the redirect issue if needed, pretty easy fix. @pernielsentikaer Any feedback will be highly appreciated, regarding the redirects I think it's irrelevant to the current PR.
We can merge this into the store, but I hope the redirect issue could be resolved since it's a blocker for me using it and I think users will be confused too
Updated and now deployed - page-speed will now follow redirects. Note that there may be other issues with dr.dk and Page Speed Inishgts in general.
Here is the improved text:
Do we need any changes to the extension as well?
I tried the following list, but all of them failed:
- dr.dk without protocol
- https://dr.dk (https)
- https://www.dr.dk (https and www)
(The problem might have been be that there was no valid API data from Google for that particular domain when page-speed runs its test. See https://pagespeed.web.dev/analysis?url=https://www.dr.dk. It sporadically gives errors for me.)
API seems working for me now though: https://page-speed.dev/api/run/dr.dk...
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
Hey @pernielsentikaer I’ve missed your comment due to flooding GitHub notifications. I am out of office so coming back to the changes ASAP in the upcoming weeks, it’s worth implementing the changes and finally merging everything
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
This issue has been automatically closed due to inactivity.
Feel free to comment in the thread when you're ready to continue working on it 🙂
You can also catch us in Slack if you want to discuss this.