{
  "trx_id": "ee93f73b90ec3d45fdd9fe590853cefa3232d16b",
  "block": 102877030,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-24T04:51:42",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "5472.996220 VESTS"
    }
  ]
}

{
  "trx_id": "6e1a40e236a67f8e6ca5790dfeb4e694436aa90f",
  "block": 91323222,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-18T00:00:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "5637.215417 VESTS"
    }
  ]
}

{
  "trx_id": "0da3bea06dedeb5ebb4ddf1b7cbd104f69ac4ddc",
  "block": 79877318,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-14T15:39:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "5806.348949 VESTS"
    }
  ]
}

{
  "trx_id": "e3a9a46a9ca98a392947bdaa972abed06d16d34a",
  "block": 78365405,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-22T12:30:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "8743.257735 VESTS"
    }
  ]
}

{
  "trx_id": "4ae4bf465d621f6bab572668d24cda11faab0ab8",
  "block": 69122830,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T19:42:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "8965.309173 VESTS"
    }
  ]
}

{
  "trx_id": "7fc1058d1f77f57a16e22a883cf54b8333d66dd2",
  "block": 59614300,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-12-06T12:55:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "9219.636575 VESTS"
    }
  ]
}

{
  "trx_id": "9263e91535ebecf46e6efbafb17ff4a539e8dd47",
  "block": 53593335,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-05-09T12:52:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "9404.067046 VESTS"
    }
  ]
}

{
  "trx_id": "16b6818d5c536c3f1f980648fd0bb99461fd5886",
  "block": 48460847,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-09T20:04:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "9592.208746 VESTS"
    }
  ]
}

{
  "trx_id": "13d17f712ef0390fdbfb10b45fcecd368174c7e6",
  "block": 48308553,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-04T10:44:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "28795.008272 VESTS"
    }
  ]
}

{
  "trx_id": "d06e30879891cbaad9c1f9dfe9d15e511bb11280",
  "block": 46699428,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-08T18:50:48",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "websitespeedtesting",
      "author": "w3spedup",
      "permlink": "google-page-experience-update-2021-and-core-web-vitals-all-you-need-to-know",
      "title": "Google Page Experience Update 2021 and Core Web Vitals: All You Need to Know!",
      "body": "Some time ago, Google announced a new ranking factor for 2021. And it caused quite a stir.\n“Page Experience” is the new ranking factor and it changes a few things.\n\nUser experience has always been integral to building a quality website but now it’ll play a bigger role than ever. You must focus on the kind of experience that your website provides your visitors.\n\nPage Experience, the new ranking signal, combines Core Web Vitals with existing user experience signals to improve the evaluation of the overall experience provided by a page.\nAlthough it is not bound to launch before late 2021, that doesn’t stop you from being proactive and adapting for the change when there is still time at hand.\n\nAnd, Google being Google, they have provided an early look into the work being done so far.\nDon’t know what Core Web Vitals are?\n\nDon’t worry! That’s why we’ve written this early guide to Core Web Vitals and Google’s latest ranking factor.\n\nGOOGLE PAGE EXPERIENCE UPDATE\nFCP\n\nThe Google page experience signal consists of the Core Web Vitals, as well as the existing page experience metrics. The existing Google page experience metrics include the following:\n\nHTTPS-security\nSafe-browsing\nMobile-friendliness\nNo Intrusive interstitials\nThese metrics aim to understand how a user will perceive the experience of a specific web page. It considers factors such as whether the page loads quickly, if it’s mobile-friendly, runs on HTTPS, if there are intrusive ads present, and if content moves around as the page loads.\n\nWeb Vitals is an initiative by Google to provide unified guidance for quality signals that are essential to delivering a great user experience on the web.\n\nThis initiative aims to simplify the landscape and help sites focus on the metrics that matter most, the Core Web Vitals. We’ll discuss more on Core Web Vitals in the following sections.\n\nYou can view Google’s detailed documentation for page experience here.\n\nCORE WEB VITALS\nIntroduced in May 2020, Core Web Vitals are a set of metrics related to speed, responsiveness, and visual stability of a website.\n\nCore Web Vitals are the subset of Web Vitals that apply to all web pages and should be measured by all site owners.\n\nAll Core Web Vitals represents a distinct facet of the user experience. Each is measurable in the field, on real users actually loading and interacting with the page. Each reflects the real-world experience of a critical user-centric outcome.\n\nGoogle has defined the following as Core Web Vitals:\n\nLargest Contentful Paint (LCP): LCP measures the loading performance of a website, or how long it takes for a page’s main content to load. LCP should occur within 2.5 seconds of when the page first starts loading, to provide a good user experience.\n\nFirst Input Delay (FID): FID measure interactivity or the time your website takes to become interactive. Ideally, you should maintain an FID of less than 100 milliseconds.\n\nCumulative Layout Shift (CLS): CLS measures the visual stability of a page or the amount of unexpected layout shift of visual content on a page. You should aim for a CLS score of less than 0.1\n\nThese Core Web Vitals are not set in stone. Chromium blog states that they expect to update Core Web Vitals on an annual basis. Although Google Developers blog states that, “The Core Web Vitals are relevant to all web pages and featured across relevant Google tools. Changes to these metrics will have a wide-reaching impact; as such, developers should expect the definitions and thresholds of the Core Web Vitals to be stable, and updates to have prior notice and a predictable, annual cadence.”\nLet us now take a look at each of the Core Web Vitals metrics in detail.\nLCP OR LARGEST CONTENTFUL PAINT\nLargest Contentful Paint (LCP) measures the time at which the largest content element appears on the screen. Please note that it does not measure the time taken by your page to fully load. It simply looks at and measures when the most important part loads.\n\nIn the case of a simple web page with only a piece of text and a large image/video, that large image/video will be considered the LCP. Since this is the largest piece of content to load on a browser, it’s bound to make an impression. By getting that largest piece of content to load quicker, your site can appear much faster. So, sometimes, it might just be as simple as optimizing that image/video itself.\n\nNow that you know what LCP is, you can start optimizing it. Your aim is to get LCP loaded in 2.5 seconds or less. Anything below 4 seconds needs less and anything above 4 seconds is considered poor by Google.\n\nThe LCP is also dynamic, since the first thing that loads might not immediately be that large image. The LCP shifts to that large image when that appears on the screen.\nLet’s take a look at an image from Google that explains how that works:\n\n\n\nIn the first image on the left, you’ll see the top menu bar with the logo and ‘Visual Stories’ section load up. This is the First Contentful Paint. Then, in the next 3 images, the headline appears as a candidate for LCP. But, in the last image, the image takes place of the headline as the LCP candidate.\n\nHOW TO IMPROVE LCP?\nAccording to Google, LCP is primarily affected by four factors:\n\nSlow server response times\nRender-blocking JavaScript and CSS\nResource load times\nClient-side rendering\nOptimizing these factors will improve your LCP score! You can check out the Google Developers blog to know more about optimizing LCP.\n\nFID OR FIRST INPUT DELAY\nFirst Input Delay measures the time taken by the browser to respond to the first interaction by the visitor. The quicker the browser’s reaction, the more responsive the page will appear. You should work on the responsiveness of your pages if you’re looking to offer a positive user experience.\n\nDelay happens when the browser is kept busy with other work in the background. So, it has loaded the page but nothing happens when you tap that button. That’s a bad experience and it leads to frustration.\n\nRemember, even if there’s just a small delay it might make your site feel sluggish and unresponsive.\n\nFID measures all interactions that take place while the page is being loaded. These are input actions like taps, clicks, and keypresses. But it does not include interactions like zooming and scrolling.\n\nGoogle’s new metrics call for an FID of less than 100ms to appear responsive.\nYou must remember:\n\nYou cannot measure the FID if there is no user interaction. This implies Google can’t simply predict the FID based on the data they have from the lab. Google needs data from real users, also called field data. This also means that this data is less controllable than lab data. This is because it collects data from users will all kinds of devices and who use them in different ways & environments.\n\nHOW TO REDUCE FID?\nAccording to Google, you can reduce FID by performing the following optimizations:\n\nReduce the impact of third-party code\nReduce JavaScript execution time\nMinimize main thread work\nKeep request counts low and transfer sizes small\nYou can check out the Google Developers blog to know more about optimizing FID\n\nCLS OR CUMULATIVE LAYOUT SHIFT\nCLS or Cumulative Layout Shift tries to determine how stably all the elements load onto your screen. It measures how often elements jump around while loading and by how much.\n\nCLS compares frames to determine the movement of elements. It takes all the points at which unexpected layout shifts happen and calculates the severity of those movements. If a user clicks the menu button and a fold-out menu appears, that doesn’t count as a layout shift since it is expected behavior.\n\nSometimes a button loads on the screen, inviting users to click it. However, in the background, there’s still a large content area being loaded. So, when the content finally loads completely, the button moves down a bit as you were about to hit it. This affects your CLS score.\n\nAds are also a common culprit of a poor CLS score since ads cause a lot of layout shifts.\nLet us take an example of multiple unstable elements, as shown by Google:\n\n\n\nIn the first frame above there are four results of an API request for animals, sorted in alphabetical order. In the second frame, more results are added to the sorted list creating an unexpected layout shift.\n\nMany complex sites have so many functionalities and elements that these are heavy to load and content gets loaded whenever it’s ready. This can often also result in content or CTAs jumping around on the screen, making room for slower loading content.\n\nHOW TO IMPROVE CLS?\nAccording to Google Developers blog, you can avoid all unexpected layout shift by adhering to the following principles:\n\nAlways include size attributes on your images and video elements, or otherwise reserve the required space with something like CSS aspect ratio boxes. This ensures that the browser can allocate the correct amount of space in the document while the image is loading.\nNever insert content above existing content, except in response to user interaction. This ensures any layout shifts that occur are expected.\nPrefer transform animations to animations of properties that trigger layout changes. Animate transitions in a way that provides context and continuity from state to state.\nOFFICIAL TOOLS TO MEASURE CORE WEB VITALS\nThere are loads of tools to help you monitor Web Vitals and improve the performance of your site. Here are the most important ones:\n\nPageSpeed Insights: Google PageSpeed Insights is a full-service measuring tool with both the field as well as lab data. It also gives you advice on what to improve.\nLighthouse: Google built Lighthouse as a tool to audit PWAs, but now it’s a great tool to monitor performance. It has several audits that PageSpeed Insights doesn’t have and it even has some SEO checks.\nTo check Core Web Vitals using Lighthouse, go to a page you want to analyze, right-click, and select “Inspect”. After that, click on the “Lighthouse” button as shown below.\n\nNow, select the categories that you want to test for and tap the “Generate Report” button.\n\n\nSearch Console Core Web Vitals report: You can now get insights from your site straight from Search Console. This is great to get an understanding of how your site is performing.\nOTHER WEB VITALS\nWhile the Core Web Vitals are the critical metrics to understand and deliver great user experience, there are other important metrics as well.\n\nThese other Web Vitals often serve as supplemental metrics for the Core Web Vitals. They help capture a larger part of the experience and assist in diagnosing a specific issue.\n\nFor example, the metrics Time to First Byte (TTFB) and First Contentful Paint (FCP) are both integral aspects of the loading experience. Both are useful in diagnosing issues with LCP.\n\nTTFB helps determine whether slow server response times are slowing your website. FCP helps determine if there are any render-blocking resources on your page.\n\nMetrics like Total Blocking Time (TBT) and Time to Interactive (TTI) are lab metrics that are important in finding and diagnosing potential interactivity issues that will impact FID.\n\nBut, these metrics are not part of the Core Web Vitals because they are not field-measurable, nor do they reflect a user-centric outcome.\n\nFINAL WORDS\nSoon, Google will incorporate a new ranking factor in its algorithm: page experience. Google developed a new set of metrics which are called the Web Vitals to measure page experience. You can find three core metrics within these Web Vitals: Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. These represent performance, responsiveness, and visual stability, the three pillars of Google’s page experience update.\nDid we miss out on something important? Let us know in the comments below.\n\nWant to know more about optimizing Core Web Vitals? Get in touch with us today, and we’ll help you out.\n\n\nhttps://w3speedup.com/",
      "json_metadata": "{\"tags\":[\"websitespeedtesting\",\"websitespeedoptimization\"],\"links\":[\"https://w3speedup.com/\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "7335cc043e5311c3d9e9ef279320e00ada9f7ea3",
  "block": 46679592,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-08T02:06:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "28987.535220 VESTS"
    }
  ]
}

{
  "trx_id": "df03c1f87273bd2cd5a71272c926392762b7e40c",
  "block": 46675862,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T22:57:27",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "w3spedup"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"w3spedup\",\"following\":\"smartum\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "7dd832fbd97865ce3e2d1e05da7e5c6b01b482b4",
  "block": 46668768,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:58:06",
  "op": [
    "vote",
    {
      "voter": "w3spedup",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-smartum-20200123t171644000z",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "7352f5b11f51814e654f3b47584497e12299e556",
  "block": 46668763,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:57:51",
  "op": [
    "vote",
    {
      "voter": "w3spedup",
      "author": "smartum",
      "permlink": "why-page-speed-is-blocking-you-from-being-in-the-top-google-searches-and-how-to-improve-the-situation",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "4ace9ffeaa1e0b1b06a742ac76f980fa034074aa",
  "block": 46668758,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:57:36",
  "op": [
    "comment",
    {
      "parent_author": "steemitboard",
      "parent_permlink": "steemitboard-notify-smartum-20200123t171644000z",
      "author": "w3spedup",
      "permlink": "qgasgs",
      "title": "",
      "body": "Very Good information indeed but if you want achieve 90+ in Google Page Insight  in Mobile and Desktop as well and Less than 3 Sec in Gt-matrix here is my publication i had started on Medium have a look at it and feel free to drop a comment if you have any query. https://medium.com/w3-speedup",
      "json_metadata": "{\"links\":[\"https://medium.com/w3-speedup\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}

{
  "trx_id": "35fec752beee9d54780dd918a48d2494b137f1c6",
  "block": 46668612,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:50:09",
  "op": [
    "transfer",
    {
      "from": "future.witness",
      "to": "w3spedup",
      "amount": "0.001 STEEM",
      "memo": "⚠️ Please be careful with any website or discord link that you receive from other users, those are mostly phishing attempts."
    }
  ]
}

{
  "trx_id": "750a02ab277ce304c8b3fe01c702961245bb0c83",
  "block": 46668590,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:49:03",
  "op": [
    "transfer",
    {
      "from": "executive-board",
      "to": "w3spedup",
      "amount": "0.001 STEEM",
      "memo": "❗ Hello w3spedup, welcome to the STEEM ecosystem. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's easy, just follow the instructions. Warm regards, The Executive Board."
    }
  ]
}

{
  "trx_id": "b8dce9d4820f8c7f64627795d86cc512e0356507",
  "block": 46668553,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:47:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "w3spedup",
      "vesting_shares": "30300.000000 VESTS"
    }
  ]
}

{
  "trx_id": "b8dce9d4820f8c7f64627795d86cc512e0356507",
  "block": 46668553,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-09-07T16:47:12",
  "op": [
    "create_claimed_account",
    {
      "creator": "steem",
      "new_account_name": "w3spedup",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM8KFEL9paVF8pHmfyD7kT5RhY9XsKZtgKe5xZB2c7J28JjG9U6Z",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM64n4CBnexuJxK8pZvQHTEMK7Rax7Vz8Mo67wBEoEgQB5NwABJf",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM8QSN6GEXeck4tzwhhhu23G3cAeuY36hfS9gqeqf4pFGnuJ5mdw",
            1
          ]
        ]
      },
      "memo_key": "STM5PULigVSXoAWKG11Jpr3Sr1wTroikgVJHghk8EvDgTZ26KH5ze",
      "json_metadata": "{}",
      "extensions": []
    }
  ]
}