Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Stats preview card component using HTML and CSS

José Alfonzo•370
@JoseAlfonzo92
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

It's a basic challenge, so no need for help at the moment — but if you spot anything off or see areas I could improve, I'd love your feedback. Always open to refining things.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PIYUSH KUSHWAH•330
    @piyushkumarx
    Posted about 1 month ago

    Areas to Improve: Padding on Small Screens:

    On very narrow screens (less than 350px), the text feels a bit too close to the edges. 👉 Add more padding: 1rem or margin-inline: auto to improve breathing room.

    Stats Layout on Mobile:

    Currently, the stats are in one row on mobile, which can feel tight. 👉 Consider stacking the stats vertically (column direction) for better readability on narrow screens.

    Font Size Scaling:

    The paragraph font size could scale slightly smaller on mobile to prevent long lines from wrapping awkwardly.

    Container Width Limit:

    On very large screens (e.g., 1440px+), the card looks too narrow in the center. 👉 You could make the max-width a bit wider or add a slight zoom effect to better use screen space.

    Marked as helpful

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.

Oops! 😬

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

Log in with GitHub