Skip to content
ReDock ReDock help

Check mail delivery and page speed in ReDock Web

Mail and speed answers two questions about every connected site. Can its mail be delivered, or is something in its DNS sending the order emails to spam? And how long does its home page take to load on a phone?

About once a week ReDock reads each site’s mail records through public DNS and asks Google’s PageSpeed Insights to load the home page the way a phone would. Both checks happen from outside and ask the site itself for nothing. They work even while the site is down, and there is nothing to set up.

Read the page

Section titled “Read the page”

  1. Open Mail and speed, under Work in the sidebar. Each site has a line with its state, its speed score, and how the score has moved since the week before.

    The Mail and speed page, open from the Work group of the sidebar, saying it shows whether the workspace’s sites can get their mail delivered and how fast they load on a phone, checked from outside about once a week. The first site is Ready with a speed score of 94, Good, up 13. Its What was found section lists the mail records for its domain: the SPF record, SPF lookups at 3 of the 10 a receiver allows, a DMARC record set to reject, and a DKIM key published at a named selector, then Nothing to fix here.

  2. Open What was found under a site. The mail records come first, for the domain named, then the speed readings.

  3. Fix what it lists. Every problem comes with a sentence saying what it means and which record to add or change. Once you have changed the DNS, the next weekly look shows the result.

The mail records

Section titled “The mail records”
Record What ReDock checks
SPF that the domain publishes one, and how many DNS lookups it costs against the 10 a receiving server allows, counted through every include
DMARC that the domain publishes one, and its policy. A subdomain with no record of its own is looked up one level higher, the way a receiving server does, and the page says which name answered
DKIM whether a key is published at any of the 16 selector names ReDock knows

The SPF row of a site that needs attention: a record with five includes, and under it the count, 14 lookups of the 10 a receiver allows.

An SPF record over ten lookups is the one that fools people. It looks correct, but past the limit a receiving server gives up on it and it protects nothing. ReDock follows every include to count, and if a chain is too long to follow to the end, the page says “at least” and warns that the real number may be higher.

A DKIM key that was not found is not proof that there is none. The selector name is chosen by whatever sends the mail and only announced inside the messages. To be certain, open a message the site sent, read the s= value in its DKIM-Signature header, and check that name.

The three record rows of a site with nothing published: SPF and DMARC both read no record published, and DKIM reads not found at any of the 16 selector names ReDock knows, which is not the same as saying there is none.

The speed readings

Section titled “The speed readings”

The score is Google’s PageSpeed Insights score for a phone, the number a client is most likely to have seen somewhere else, with Good, Needs work or Poor beside it. Three readings sit under it.

Reading What it measures
Largest Contentful Paint how long a visitor waits before the biggest thing on the screen has appeared
Interaction to Next Paint how long the page takes to respond after somebody taps or clicks
Cumulative Layout Shift how much the page jumps about while it is still loading

Speed, on a phone: three cards reading Largest Contentful Paint 1.9 seconds, Interaction to Next Paint 140 milliseconds and Cumulative Layout Shift 0.02, each with a line saying what it measures, and a note that these come from real visits to this site, collected by Chrome.

The line under the readings says where they came from. On a site with enough visitors, they are Google’s measurements of real visits in Chrome. On a quieter site, the first and last come from Google’s own test load of the page, and Interaction to Next Paint reads no reading, because it can only be measured from real visits. ReDock leaves that gap empty rather than filling it with a number from somewhere else.

Speed, on a phone, for a quieter site: Largest Contentful Paint 3.2 seconds, Cumulative Layout Shift 0.08, and Interaction to Next Paint showing no reading, with a sentence saying it can only be measured from real visits and this site has too few. A note says these come from Google’s own test load of the page.

If the speed check could not run in a given week, the score reads not checked, never zero. The mail records are checked either way.

A site you just connected

Section titled “A site you just connected”

A newly paired site shows Waiting until its first look, which comes on its own within five days. Nothing is needed from you or from the site.

A site paired this morning, marked Waiting and not looked at yet, with its first look due within 5 days of pairing. Its What was found section says the site has not been looked at yet, and that the first check runs on its own within the week and needs nothing from you or from the site.

Open ReDock Web, or create an account if you do not have one yet.