sitespeedio / dashboard.sitespeed.io Goto Github PK

Hello sitespeed-team,

We are using the dashbord to measure performance data from our website.
I created a js-File in

/opt/sitespeedio/dashboard/tests//desktop/scripts

with the following content

module.exports = async function(context, commands) {
  // We start by navigating to the login page.
  await commands.navigate(
    'https://<URL>'
  );

  // When we fill in a input field/click on a link we wanna
  // try/catch that if the HTML on the page changes in the feature
  // sitespeed.io will automatically log the error in a user friendly
  // way, and the error will be re-thrown so you can act on it.
  try {
    // Add text into an input field, finding the field by id
    try {
         await commands.addText.byId('<USER>', 'principal_name');
         await commands.addText.byId('<PASSWORD>', 'password');

         // Find the sumbit button and click it and then wait
         // for the pageCompleteCheck to finish
         await commands.click.byIdAndWait('submit');
         await commands.wait.byTime(2000);
         await commands.screenshot.take('screen_login_success');
    } catch (e) {
         commands.error('Add value not possible');
         await commands.screenshot.take('screen_login_failed');
    }
    // Measure the site page as a logged in user

// click to open groupware
    await commands.measure.start('Loading groupware');
    try {
       await commands.click.byXpathAndWait('/html/body/div[1]/div[2]/div[1]/div[3]/a');
       await commands.screenshot.take('screen_groupware');
    } catch (e) {
         commands.error('groupware not working');
         await commands.screenshot.take('screen_groupware_failed');
    }
    await commands.measure.stop();


// Logout         
    await commands.screenshot.take('screen_before_logout');
    try {
      await commands.click.byXpathAndWait('/html/body/div[1]/div[2]/div[3]/div[2]/a');
      await commands.screenshot.take('screen_success_logout');
    } catch (e) {
      commands.error('Logout not possible');
      await commands.screenshot.take('screen_logout');
    }
    return await commands.screenshot.take('screen_after_last_stop');
  } catch (e) {
    context.log.error(e);
    await commands.screenshot.take('fail_complete');
    // We try/catch so we will catch if the the input fields can't be found
    // The error is automatically logged in Browsertime and re-thrown here
  }
};

As you seen we take a screenshot after every commands.click.byXpathAndWait command.
Now I would like to know if it's possible to compare this created screenshot with another screenshot to find out if the site is available and measure what we expected?
If not a error message should be issued.

We want to make sure that the page is as we expected. So if it's not possible to compare the screenshot/jpeg files we could also imagine that a string is compared.

Or is there another way to find out if a page is unavailable?

Thanks you very much in advance.

Hi, I have just started to learn how to use sitespeed.io for my projects and I am able to setup the grafana in Digital Ocean. While I am testing this script to continuously run the test, I meet some issues.

1. I am using exactly the same settings in this repo and only modify the necessary like graphite host/auth, URLs to test in desktop.txt and etc.
2. I am testing multiple pages in multiple domains.
   Example:
   abc.com
   abc.com/products
   abc.com/about-us
   def.com
   def.com/products
   def.com/about-us
3. I am assuming the results will be stored in separate folder under abc.com/def.com folder. But it is currently stored as following:
   /sitespeed-result/abc.com/[DATE]/pages/abc.com
   /sitespeed-result/abc.com/[DATE]/pages/def.com

May I know if this can be configured to do as below?
/sitespeed-result/abc.com/[DATE]/
/sitespeed-result/def.com/[DATE]/

Dear sitespeed-team,
dear @soulgalore ,

we use the sitespeed dashboard to measure the response times of a website.
With the dashboard it is possible to check the website via the txt file and the Json file.

The code in the "run.sh" file looks like that

for url in tests/$TEST/desktop/urls/.txt ; do
[ -e "$url" ] || continue
for browser in "${BROWSERS[@]}" ; do
POTENTIAL_CONFIG="./config/$(basename ${url%%.}).json"
[[ -f "$POTENTIAL_CONFIG" ]] && CONFIG_FILE="$(basename ${url%.}).json" || CONFIG_FILE="desktopWithExtras.json"
NAMESPACE="--graphite.namespace sitespeed_io.$(basename ${url%%.})"
docker run $DOCKER_SETUP $DOCKER_CONTAINER $NAMESPACE CONFIG/$CONFIG_FILE -b $browser $url
control
done
done

The file contains a URL on each line.

However, if we test the website in this way, we get a response time that does not match the perceived website call at all.
In order to find out why time is so different, we have activated the recording of a video in the dashboard as follows:

file "config/desktop.json"
{
"extends": "/config/secrets.json",
"browsertime": {
"connectivity": {
"engine": "external",
"profile": "native"
},
"visualMetric": true,
"visualElements": true,
"iterations": 1,
"browser": "chrome",
"video": true,
"chrome": {
"timeline": true,
"collectConsoleLog": false,
"enableTraceScreenshots": false
},
"firefox": {
"includeResponseBodies": "all",
"disableBrowsertimeExtension": true,
"windowRecorder": false,
"geckoProfiler": true
},
"pageLoadStrategy": "none",
"pageCompleteWaitTime": 0,
"pageCompleteCheckStartWait": 0,
"pageCompleteCheckPollTimeout": 0
},
"cpu": false,
"gzipHAR": false,
"html": {
"fetchHARFiles": true,
"showScript": false,
"compareURL": "https://compare.sitespeed.io/"
},
"plugins": {
"remove": ["axe","sustainable"]
},
"screenshot": {
"type": "jpg"
}
}

The videos are also created. However, if we look at the videos from this URL, we see that "resolving host" is displayed at the bottom left for a very long time when the website is opened. This also explains why the call takes so long.

Since we cannot explain this, we also called the URL via the Json file.
The content of the Json file looks like this:

module.exports = async function(context, commands) {
await commands.measure.start('https://URL-here/', 'Landingpage');
return await commands.screenshot.take('screen_website');
};

However, these videos from this call are only with white content.

Why does it take so long to access the website with the txt file (resolving host problem)?

We would be really happy if you could help us. We would like to continue using sitespeed, but we cannot explain the times.

Thanks your
Danny

Hi,

Sorry if I asked this question in wrong page.
I was trying to run this form my aws ec2.

I followed all the instruction from https://www.sitespeed.io/documentation/sitespeed.io/performance-dashboard/#up-and-running-in-almost-5-minutes following a video form youtube https://www.youtube.com/watch?v=1hGqucegbiE.

Every steps works under "Up and running in (almost) 5 minutes" , and after 3rd step my test results did not list in my aws grafana Dashboard. I ran alot of site using the step 3, but none of the site showed up in aws Dashboard, it just still shows the default Dashboard..

Command ran in aws linux: docker run --rm -v "$(pwd)":/sitespeed.io sitespeedio/sitespeed.io:13.3.2 --graphite.host=host.docker.internal https://www.mytestsitessss.com

Will there be any missing steps which I might have missed..plz help....

Hi there,

Just looking into this, and wondering - how do we set it up so it runs the tests once a day (for example)?

Thanks!

Some of the dashboards contain "NO DATA" - maybe you should monitor the data sources? :)

I am trying to analyze 2 different domains, approximately 5-8 pages from each.
I edited file "desktop.txt" and included all of the URLs, file sample here:
desktop.txt

So, finally file structure looks like: "first_domain_in_desktop.txt/pages/BOTH_DOMAINS"

Dear sitespeed-team,
we are using sitespeed dashboard to monitoring and analyze some of our websites.
I added some lines of our website in the file

../tests/FOLDERNAME/desktop/urls/startpage.txt

One every run I get an following error in /tmp/.log

Google Chrome 80.0.3987.132
Mozilla Firefox 74.0
[2020-04-01 13:06:36] INFO: Versions OS: linux 4.15.0-72-generic nodejs: v12.13.0 sitespeed.io: 12.3.1 browsertime: 8.3.1 coach: 5.0.1
[2020-04-01 13:06:36] INFO: Running tests using Chrome - 1 iteration(s)
[2020-04-01 13:06:38] INFO: Testing url URL iteration 1
[2020-04-01 13:07:37] INFO: URL 20 requests, backEndTime: 8.18s, firstPaint: 16.32s, firstVisualChange: 16.33s, DOMContentLoaded: 16.36s, Load: 24.28s, speedIndex: 16414, perceptualSpeedIndex: 16681, contentfulSpeedIndex: 16337, visualComplete85: 16.33s, lastVisualChange: 24.33s, rumSpeedIndex: 16505
[2020-04-01 13:07:38] INFO: The server responded with a 404 status code for https://URL/favicon.ico
[2020-04-01 13:07:41] INFO: HTML stored in /sitespeed.io/sitespeed-result/URL/2020-04-01-13-06-36
./sitespeed.run found. Make another run ..

I also getting the INFO message when I'm using javascript.

Now my first question: Is the absence of the favicon also included in the calculation of the time?
Secound question: It is possible to disable downloading the favicon?

Thank you very much

config/crux.json in the respository extends /config/crux.json. Can you share sample contents for /config/crux.json? Is it same as /config/secrets.json?