Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Responsive Website make of using HTML ,CSS & BOOTSTRAP.

bootstrap
haldarmanik•60
@haldarmanik
A solution to the Space tourism multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Why white blinking when click navigation bar link ?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jesse Ohanugo•110
    @J-e-s-se
    Posted about 3 years ago

    Just set your background to a dark color.

  • Harsh•210
    @HarshPrateek559
    Posted about 3 years ago

    You are not alone with that white flash problem. Everyone who attempted this project experienced this problem. I also could not find how to fix it, although I do know why it happens.

    It happens because when your website is loaded for the first time, it has to load all the images and other assets. When this happens for the first time, the assets are loaded a little later than the body of the web page, thus what appears as a white flash is just the white body of the webpage which is covered by the background image as soon as it gets loaded.

    I would advise you to not get into that stuff. Your website is already looking pretty neat, what you can do instead is make the website with React so that it does not reload every time a link is clicked. It would be a great upgrade and could very well become your first step in Javascript Frameworks.

    You can also make the buttons round in CSS if you like with the border-radius of 50%, and make the height and width of the buttons equal. I would look much better that way and would be way closer to the original design.

    Hope these suggestions would help😊.

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

Oops! 😬

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

Log in with GitHub