Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Optimize SEO and performance to achieve 100 PageSpeed score #202

Closed

Conversation

yogithesymbian
Copy link
Contributor

@yogithesymbian yogithesymbian commented Jan 2, 2025

What will change?

  • Implemented meta tags for better SEO (title, description).
    pagespeed

Learnings

Currently, if you paste your URL (e.g., https://yourdomain.com) into chat apps or social media, it only appears as plain text without any additional information. With these configurations, we can display a title and description, and achieve a perfect 100 score on Google PageSpeed Insights. Making these changes the default code would be an even better approach. Would you suggest adding it to the .env.example file or hardcoding it as done in this PR? If it looks good, feel free to merge! 😄

Security

Before you click Merge, take a step back and think how someone could break the Confidentiality, Integrity and Availability of the code you've just written. Are secrets secret? Is there any sensitive information disclosed in logs or error messages? How does your code ensure that information is accurate, complete and protected from modification? Will your code keep Contentful working and functioning?

@yogithesymbian yogithesymbian requested a review from a team as a code owner January 2, 2025 06:08
Copy link

vercel bot commented Jan 2, 2025

@yogithesymbian is attempting to deploy a commit to the Contentful Apps Team on Vercel.

A member of the Team first needs to authorize it.

@andipaetzold
Copy link
Contributor

Thanks for the PR and for bringing up this issue!
Your proposed changes are not quite enough as they are not dynamic for the individual blog post pages. I created another PR that always uses the current page's SEO fields: #204.

I close this PR as it's no longer needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants