API tools faq
paste
clickio

NovaGente CLS reccomendations

clickio
May 15th, 2026
5,110
0
Never
1
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.12 KB | None | 0 0
raw download clone embed print report
  1. CLS Improvement Recommendations.
  2. Background: CLS score is currently at 71% (Poor). Detailed analysis confirmed that the degradation occurs specifically in the Android WebView environment — primarily traffic coming from the Facebook in-app browser. Chrome, Safari, and Opera are unaffected because their browsers maintain a persistent font cache across sessions. Android WebView runs in an isolated process with no access to that shared cache, meaning Google Fonts are fetched from the network on every single visit. Combined with render-blocking scripts that delay font requests, users consistently see layout shifts before fonts arrive.
  3.  
  4. Two root causes were identified and confirmed via PerformanceObserver measurement.
  5.  
  6. Fix 1 — Self-host web fonts with font-display: swap (Highest Priority)
  7. Why: Google Fonts are loaded from fonts.googleapis.com and fonts.gstatic.com. In Chrome and Safari these are cached between sessions and load instantly. In Android WebView (Facebook in-app browser) this cache doesn't exist - every page view requires a full round-trip to Google's servers: DNS resolution → connection → CSS fetch → a second round-trip for the actual .woff2 files. By the time fonts arrive, the page is already visible to the user with a system fallback font. When the web fonts swap in, the H1 headline changes from 3 lines to 2 lines, causing a ~20px layout shift (CLS value: 0.014 — this is 82% of the total measured CLS).
  8.  
  9. What to do: Download and self-host the following font families currently loaded from Google Fonts:
  10.  
  11.  
  12.  
  13. PT Sans — weights: 400, 400italic, 700italic, 700
  14. Lato — weights: 300, 400, 700, 900
  15. Ubuntu — weights: 300, 400, 500, 700
  16.  
  17. Tools for generating self-hosted packages: google-webfonts-helper.herokuapp.com or fontsource.org.
  18.  
  19. Place the .woff2 files on the same domain (e.g. /fonts/) and declare each @font-face with font-display: swap. Example for Lato Bold:
  20.  
  21.  
  22.  
  23. @font-face {
  24. font-family: 'Lato';
  25. font-style: normal;
  26. font-weight: 700;
  27. font-display: swap;
  28. src: url('/fonts/lato-700.woff2') format('woff2');
  29. }
  30.  
  31. Remove the existing <link> to fonts.googleapis.com from the <head> once self-hosting is in place.
  32.  
  33. Optional but recommended — add a metric-compatible fallback font using size-adjust so that the layout does not shift even when the web font is not yet loaded:
  34.  
  35.  
  36.  
  37. @font-face {
  38. font-family: 'Lato-fallback';
  39. src: local('Roboto'), local('Arial');
  40. font-weight: 700;
  41. size-adjust: 97%;
  42. ascent-override: 99%;
  43. descent-override: 22%;
  44. }
  45.  
  46. Then in the heading CSS: font-family: 'Lato', 'Lato-fallback', sans-serif; — this makes the fallback and the web font occupy the same height, so the swap produces zero layout shift.
  47.  
  48. Fix 2 — Add font-display: swap to FontAwesome (Medium Priority)
  49. Why: The self-hosted FontAwesome font (fontawesome-webfont.woff) loads at ~3890ms with no font-display declaration, which defaults to block behavior. This causes icons to be invisible until the font arrives and may contribute to secondary layout shifts.
  50.  
  51. What to do: Locate the @font-face declaration for FontAwesome in the site's CSS (file: css_JkdeNoJmSZ4d_...css) and add font-display: swap:
  52.  
  53.  
  54.  
  55. @font-face {
  56. font-family: 'FontAwesome';
  57. font-display: swap; /* add this line */
  58. src: url('...fontawesome-webfont.woff2') format('woff2'),
  59. url('...fontawesome-webfont.woff') format('woff');
  60. }
  61. Fix 3 — Eliminate render-blocking JavaScript (Medium Priority)
  62. Why: There are currently 8 render-blocking tasks loaded in <head> without async or defer. These scripts hold up the browser's HTML parser and delay the discovery and loading of web fonts. The total blocking time measured is up to ~464ms per script. In a fast browser on a good connection this is tolerable; in Android WebView on a mobile network it directly extends the FOUT window and worsens CLS.
  63.  
  64. The following scripts are blocking the main thread on every page load:
  65.  
  66. File: Block duration
  67.  
  68. jquery.min.js (http://ajax.googleapis.com/)
  69.  
  70. ~365ms
  71.  
  72. bootstrap.min.js (http://cdn.jsdelivr.net/)
  73.  
  74. ~464ms
  75.  
  76. js_aczm2rRgH_...Co.js (http://novagente.pt/)
  77.  
  78. ~342ms
  79.  
  80. js_Xk8TsyNfILci...O4.js (http://novagente.pt/)
  81.  
  82. ~350ms
  83.  
  84. js_6uMVSUgDf9l...U.js (http://novagente.pt/)
  85.  
  86. ~353ms
  87.  
  88. js_HMpo5_qEBJg...g.js (http://novagente.pt/)
  89.  
  90. ~353ms
  91.  
  92. js_9AO-H4BaoI7...o.js (http://novagente.pt/)
  93.  
  94. ~362ms
  95.  
  96. js_oYVKp-cluFZ...w.js (http://novagente.pt/)
  97.  
  98. ~418ms
  99.  
  100. What to do: These scripts need to be loaded non-blocking. Add async or defer to each of them — the appropriate attribute depends on whether each script has dependencies on others (your developer will know which applies in each case). This change needs to be evaluated carefully to avoid breaking functionality, but the goal is straightforward: none of these scripts should be blocking the main thread during initial page render.
  101.  
  102. Expected outcome: Fixes 1 and 2 together directly eliminate the two confirmed CLS sources (FOUT on Lato and PT Sans), which account for 100% of the measured layout shifts. Fix 3 reduces the FOUT window as a complementary measure. Combined, these changes should move the CLS score from 71% to 80%+ for the Android WebView segment.
Advertisement
Comments
  • olegstamm
    olegstamm
    2 days
    # CSS 0.86 KB | 0 0
    view report reply
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1wblDBMJxT9Q3AmnrHH18pdJjRjRFGzsVIoODC6CGK6s/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 25% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from SimpleSwap — instant swap).
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!