Skip to content

Load Testing Blog

Page Response time Perception

The visibility of a website or a web page in a search engine's unpaid results depends on its loading speed. Since 2010, Google announced that Webmasters should optimize their web pages loading speed because it's going to be a ranking criteria: Page speed and Search Engine Ranking. Matt Cutts predicted this change on his blog.

Moreover, global website performance is also important for your visitors. Most people dislike when a website is stuck loading the page, and leave without coming back. With internet being faster and faster, people become more impatient and refuse to wait.

With increasing network speed, both on mobile and desktop, users are used to quick page loading. This would have been a completely different story when users were connecting using 56k. Did you know that most people leave a website after 2 seconds of waiting?

Why We Chose JMeter

When we started to think how to build OctoPerf, about one year ago, we had several options to create our stress testing platform:

  • Write our own HTTP engine from the ground,
  • Use command line tools like Curl,
  • Reuse an existing open-source HTTP engine, but which one? (Gatling Tool, JMeter, Grinder...)

It took us several months to choose which one was the right option. When you are building a startup, the biggest constraint is obviously Time. It is the limitation factor.

But, you must spend the right time on your product to bring value to the customers.

Writing Our own Engine from scratch

public static void main(String[] args) {
    SpringApplication.run(Application.class, args);
}

Our Philosophy

We are proud to announce the opening of our Tech Blog. We really wanted to have a place to share technical thoughts openly. Why so open? Sharing technical stuff on our platform is like releaving secrets about how we built OctoPerf, our SaaS load testing tool.

OctoPerf wouldn't exist without the open-source community.