Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Static job listings master project

accessibility, bootstrap, sass/scss
cmb347827•900
@cmb347827
A solution to the Job listings with filtering challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

This one was more complicated to submit and have a visible project screenshot. But it works, seems bug free, and I finished it .

What challenges did you encounter, and how did you overcome them?

I needed help with getting the project screenshot to be a fully loaded normal design image. I had to ask at Discord and someone pointed me in the right direction (by mentioning Lighthouse ), and I googled the name , added the extension to my brouwser and it pointed me to areas that were too slow , or causing a slower load.

I fixed those problems as best as I could . Finished with a performance score of 96, accessiblity score of 91, best practices score of 100, and seo score of 91 (as of nov 9 2024).

What specific areas of your project would you like help with?

Clearly , I need to dive deeper into how to avoid/eleminate 'render blocking resources' firstly. I'm mostly confused by this error , as I've always learned that you need to keep styling/semantics separate , and now (for the first time) I hear that no, you should not do that as it causes the fist load to be too slow.

I'm very frustrated by this as I have no idea how to avoid these errors in the future, without having to keep all my css separate in the `

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on cmb347827'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

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.