The first step is to identify the username and password fields. We will use CSS selectors to identify the two fields. You can find additional information about retrieving CSS selectors in this post.
We will use the Browshot login page as an example: https://browshot.com/login. This page has two forms, the first of which is used to log into the dashboard.
Sometimes, pages display banners or overlays—such as cookie banners, subscription popups, etc.—that hide the pages’ main content. With Blitapp, you can hide these banners and overlays before taking a screenshot of the page.
We’ll go through a couple of examples to explain how to find the element to hide or click on, as well as how to add it to your capture settings. If you find this post too complicated and aren’t sure how to hide elements for your captures, don’t hesitate to contact us for assistance.
The news website The Guardian (https://www.theguardian.com/us) asks the user to accept cookies with a banner at the bottom of the page.
Blitapp used to take screenshots as JPEG files. When we took over Blitapp, we switched to better quality PNG images. But these PNG files can have a much larger size size, going over 15MB for a full page screenshot.
Now, you have a choice between JPEG and PNG for all you captures. Click on Advanced Web Options, you will find the new option *Image Quality” to switch between PNG and JPEG.
To give you an idea of the file size and quality for both formats, here are a couple of examples. You can open both images in new tabs to compare the quality:
Amazon product page, 1,280 x 7,941px
Instagram homepage, 1,280 x 10,830px
The difference in terms of file size gets bigger as the screenshot size is bigger, but also depending on how “busy” is the web page.more...