Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Designo Agency Website using Astro.js, Tailwind CSS & React Hook Forms

astro, lighthouse, react, tailwind-css, typescript
Jakub Jirous•270
@jakubjirous
A solution to the Designo multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey fellow developers and Astro.js enthusiasts!

I've been hard at work building Designo Agency Website using Astro.js to ensure the best possible performance, accessibility, and SEO. However, I've hit a few roadblocks and uncertainties along the way. I would greatly appreciate your valuable insights and experiences to help me deliver 100% results in Lighthouse across these crucial aspects.

What strategies have you found most effective in achieving optimal performance scores in Lighthouse using Astro.js?

How do you approach accessibility considerations when working with Astro.js?

What steps have you taken to ensure your Astro.js website ranks well in search engine results?

How have you effectively integrated external libraries or plugins into your Astro.js projects without compromising performance or accessibility?

I truly value your expertise and experiences, and I believe that by sharing our insights, we can collectively elevate the Astro.js development community.

Thank you in advance for taking the time to help me fine-tune my website for exceptional performance, accessibility, and SEO.

Happy coding!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Jakub Jirous's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.