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

Responsive landing page with single introductory section with HTML/CSS

accessibility
Djamel1133•910
@Djamel1133
A solution to the Huddle landing page with a single introductory section 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?

Mobile first approach ....

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

Any feedback is welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Houari Aouinti•1,850
    @aouintihouari
    Posted 8 months ago

    Well done! Keep practicing and improving.

    However, I've noticed that you've used the @import in your CSS file rather than linking them directly in your HTML. For a very small and simple project like this one, it's not a problem, but you should know that it's not a best practice. You should link the fonts directly in your HTML for better performance.

    Linking fonts directly in the HTML <head> is better for performance due to a few key reasons:

    1. Early Loading: The browser can start loading the font as soon as it encounters the <link> tag, reducing the time it takes for the font to be available for rendering.

    2. CSS Parsing: When using @import, the CSS file must be fully loaded and parsed before the font can be requested, adding an extra step that can delay font availability.

    3. Parallel Requests: Linking directly allows the browser to initiate multiple requests simultaneously, which can improve overall loading speed compared to the sequential nature of @import.

    4. Reduced Render Blocking: Using a direct link can help avoid blocking rendering, allowing the page to display content faster.

    Overall, these factors contribute to a smoother user experience and better performance metrics for your site.

    Marked as helpful
  • Djamel1133•910
    @Djamel1133
    Posted 8 months ago

    Thank you, I appreciate your comment and i'll fixed it soon inch Allah

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 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

Oops! 😬

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

Log in with GitHub