Rigor Product Suggestions

  1. Show average, slowest, and fastest time by page in page performance reports.

    In addition, the ability to export page performance report data as a CSV or the option to include page level data in custom reports would allow better use of real browser checks (no need to create one for each step of a funnel to export and share with the team).

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

    We are right now in the middle of reworking our data storage and aggregation system for RBC and Page Performance Report. When finished (Should be very soon), we will be providing the mean, median, max, and min for all the stats available for all the Page Performance report metrics (including some new ones like Fully Loaded)

  2. Change status report time metric to milliseconds

    Current status pages show average times in seconds. This is a very coarse metric and could be more useful reported as milliseconds. Can you please allow for it to be customized, or simply changed to milliseconds? The distance between 3s and 4s is quite a lot, and seeing specific numbers would be useful.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Incorporate Speed Index metrics in the data point detail page

    Incorporate Speed Index into the times reported for each data point...

    https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index

    Google and webpagetest.ord have started to use a measurement called Speed Index in their reporting.

    Long story short, this is a method of measuring render time to the user based on what shows on their screen (video capture) as opposed to a particular element loading or the onload event. Speed Index, as I understand it, gives a much better idea of how the page performs from the user's perspective.

    If this metric could be displayed between Render Time and Load Time, (here https://my.rigor.com/checks/10488/runs/862529159 )that would be awesome. In…

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  4. Add monitoring for ssl cert expiration

    It would be helpful to have a monitor for ssl cert expiration. For some shops that manage multiple applications with both third party and self signed certs it's a huge ordeal to manage them with a spreadsheet and sheer will.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    The ability to enforce SSL certification verification (aka fail the run if the SSL certificate isn’t valid) is currently in private beta, and will be coming out to the general public by the end of this month (Dec 2016)

  5. Show page size trends over time

    It would be great if we could see the trend of page size over time. Example: something updates on a site that greatly increases page size, users should be able to filter a trend report on page size for individual runs and spot that spike.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →

    Roberta is reworking all the data collection systems and aggregation systems, so all the metrics from the Page Performance report (including Total Page Size) will be graphable at the run and aggregate level

  6. DNS Resolution Time at the Check level instead of just the Run level

    It may be useful to roll DNS Resolution Time data up to the Check level, as with Response Time and Availability. Currently this data is only available down at the individual Run level, making it tedious to get a feel for how the DNS resolution of a given URL is performing, or if it's having systemic problems.

    This could also be helped by making Run-level data easier to query via the API. Currently, you can only get one Run's data at a time, and to do that requires having a Run ID. There is no programmatic way to get a…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
  • Don't see your idea?

Rigor Product Suggestions

Feedback and Knowledge Base