How does Silktide see websites?
Silktide does not see a webpage like most software. Instead Silktide sees pages almost exactly as real users do – in a real web browser.
This means we can see a tremendous range of content and detail that most other software cannot.
Silktide versus traditional bots
|Pages are tested in both mobile and desktop devices.||Simulation of a device is impossible, no distinction can be made between mobile or desktop.|
|Can interact with pages just like a person would, e.g. logging in, performing searches, and testing these features work.||Interaction is not possible.|
|Full pages are loaded just like a real person, including images, scripts, fonts, styles. Accurate testing of all parts of a page is possible. For example, we can assess font size, mobile layout, color contrast and more.||Only the code for the page is loaded. Only testing of that code possible.|
|Able to measure how long pages take to become interactive (usable) in real browsers.||Only able to test how long page code takes to be transmitted.|
Imagine you were trying to measure the intelligence of a person.
One way to do this would be to measure the physical properties of their brain, like its cells, size and weight.
A better way would be to talk to the person and assess their behaviour.
This is analogous to what website analysis tools do. Most traditional tools can only see the raw code (in this analogy, their brain). Silktide can experience the result of that code (talking to them).
The difference is between assessing the parts, and assessing what they do.
For example, the HTML code for a page is usually the same, whether it is viewed on a desktop or a mobile device. But the end result can be completely different, and that same code may not even work on mobile. Looking at just the code can never tell you this, which is why we look at the end result.
Silktide loads each webpage in the Chrome browser, which allows us to simulate a wide range of devices accurately. Our standard devices are as follows:
- Desktop – A Windows desktop PC using Chrome
- Mobile – A portrait iPhone 5 using Safari (this is intentionally old, so as to cover the smallest mobile screen size, a requirement of WCAG 2.1)
We gather a tremendous amount of data from each page for testing, including:
- A screenshot of the page, as it appeared in our device.
- The layout of the page, e.g., what areas appear off the side, or below the fold.
- List of all resources (images, stylesheets, etc.) and redirections used, including their timings.
- The interactive state of the page over time, e.g., when could a page be used, when was it finished.
- The font size, typeface, color and contrast of all text areas of the page.
- And much more.
- How devices are simulated
The following areas are covered when impersonating a given device (e.g., an iPhone):
- The pixel and logical pixel resolution
- The user agent
- Explicit and calculated viewports (e.g. zoom to fit)
- Device capabilities (e.g., Flash is not possible on mobile)
- Bandwidth (e.g., 3G or 4G connectivity for mobile)
Most of Silktide’s analysis is conducted on the resulting computed source.
- How does Silktide detect cookies?
- How does Silktide choose which pages to test?
- What browsers does Silktide support?
- How does scoring work?
- Why doesn't Silktide offer an accessibility plugin or overlay?
- What languages does Silktide support?
- What IP address and user agent does Silktide use?
- How does Silktide count pages?
- How does Silktide handle frames and iframes?
- How does Sitebeam compare with Silktide?
- How long does a website take to test?
- How does Silktide security work?