Every member is loaded in a real browser at four screen sizes to see whether its
webring links are there, point at the right neighbors, say who those neighbors
are, and can be found without scrolling.
Last checked 1 hour ago.
-
D40
-
No webring widget −60 no link to the ring or to either neighbor Add a widget linking to /{slug}/prev and /{slug}/next.
-
-
D54
-
Ring links need scrolling −30 the reader has to scroll 2 screens on desktop, 1 screen on wide, 1 screen on tablet, 3 screens on mobile Move the widget into the first screen.
-
Widget does not name its neighbors −10 the links say next and previous without saying who they are Show who prev and next are, not just arrows.
-
Widget is hard to tap −6 the links are 22px across on a phone, under the 24px a finger needs Make the links big enough to tap on a phone.
-
-
C56
-
Ring links need scrolling −28 the reader has to scroll 2 screens on desktop, 1 screen on wide, 1 screen on tablet, 2 screens on mobile Move the widget into the first screen.
-
Widget does not name its neighbors −10 the links say next and previous without saying who they are Show who prev and next are, not just arrows.
-
Widget is hard to tap −6 the links are 18px across on a phone, under the 24px a finger needs Make the links big enough to tap on a phone.
-
-
C60
-
Ring links need scrolling −30 the reader has to scroll 2 screens on desktop, 1 screen on wide, 1 screen on tablet, 3 screens on mobile Move the widget into the first screen.
-
Widget does not name its neighbors −10 the links say next and previous without saying who they are Show who prev and next are, not just arrows.
-
-
B79
-
Ring links need scrolling −15 the reader has to scroll 1 screen on desktop, 1 screen on tablet, 2 screens on mobile Move the widget into the first screen.
-
Widget is hard to tap −6 the links are 24px across on a phone, under the 24px a finger needs Make the links big enough to tap on a phone.
-
-
B82
-
Ring links need scrolling −2 the reader has to scroll 1 screen on mobile Move the widget into the first screen.
-
Widget does not name its neighbors −10 the links say next and previous without saying who they are Show who prev and next are, not just arrows.
-
Widget is hard to tap −6 the links are 14px across on a phone, under the 24px a finger needs Make the links big enough to tap on a phone.
-
-
B87
-
Ring links need scrolling −2 the reader has to scroll 1 screen on mobile Move the widget into the first screen.
-
Widget does not link to the ring −5 nothing links back to the ring itself Link the ring itself so visitors can find the other members.
-
Widget is hard to tap −6 the links are 16px across on a phone, under the 24px a finger needs Make the links big enough to tap on a phone.
-
-
A90
-
Ring links need scrolling −10 the reader has to scroll 1 screen on desktop, 1 screen on mobile Move the widget into the first screen.
-
What is checked
-
Site is down
-
Page did not render
-
No webring widget Add a widget linking to /{slug}/prev and /{slug}/next.
-
Widget points at another member Replace the copied slug with your own.
-
Ring links are invisible The links render with no visible box; check the CSS hiding them.
-
Neighbor links are out of date Link through the ring instead of naming neighbors directly.
-
Widget link is dead The ring no longer answers for this slug; check it is still the one you registered.
-
Widget only works with JavaScript Put the links in the HTML so they work with scripts off.
-
Ring can only be walked one way Add the missing direction so the ring can be walked both ways.
-
Ring links need scrolling Move the widget into the first screen.
-
Widget does not name its neighbors Show who prev and next are, not just arrows.
-
Widget does not link to the ring Link the ring itself so visitors can find the other members.
-
Widget is hard to tap Make the links big enough to tap on a phone.
-
Page is slow to appear The page takes a while to appear; visitors may leave first.
-
Site moved to another host Update the URL you registered with the ring.