Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Loopstudios Landing Page

Dre•610
@hadreemustaffa
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I welcome any constructive feedback. This is my first time using .webp images, just trying it out. Is my way of changing the images using <picture> tag correct?

Thank you in advance.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Faisal•5,095
    @afrussel
    Posted over 1 year ago

    Hi @hadreemustaffa

    Your code appears to use the <picture> element correctly for responsive images by utilizing <source> tags with different media queries to provide different image sources based on screen sizes. However, without specific details about the problem you're facing, it's challenging to pinpoint the issue accurately.

    Here are a few general pointers to check:

    1. File Paths: Verify that the paths to your images are correct (src and srcset attributes). Ensure the images are in the specified locations relative to your HTML file.

    2. Media Queries: Double-check your media queries in <source> tags to confirm they match the intended screen sizes. This ensures the correct image is loaded based on the device's resolution.

    3. Fallback <img> Tag: Confirm that the <img> tag inside each <picture> element provides a default image (src) for browsers that don't support the <picture> tag or media queries.

    If images are not displaying as expected, check your browser's developer tools for any console errors or warnings that might provide insights into the issue.

    By addressing these points, you might identify and resolve the problem with your <picture> tags. If you have specific errors or unexpected behaviors, providing that information would help in giving more precise assistance.

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

Oops! 😬

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

Log in with GitHub