Tools & Wizards About Us
briefly.app screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

briefly.app

Briefly. Affordable PR service for Small Businesses.

Page Load Speed

1.1 sec in total

First Response

205 ms

Resources Loaded

864 ms

Page Rendered

69 ms

briefly.app screenshot

About Website

Welcome to briefly.app homepage info - get ready to check Briefly best content right away, or after learning these important things about briefly.app

Briefly offers affordable PR services to Small and Medium sized businesses in a user-friendly platform without the need for an agency or expensive fees.

Visit briefly.app

Key Findings

We analyzed Briefly.app page load time and found that the first response time was 205 ms and then it took 933 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

briefly.app performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value1,250 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value1.584

0/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

briefly.app

205 ms

tp.widget.bootstrap.min.js

47 ms

icon

54 ms

quill.snow.css

105 ms

main.94c6de74.js

266 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 14% of them (3 requests) were addressed to the original Briefly.app, 14% (3 requests) were made to Googletagmanager.com and 10% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (266 ms) belongs to the original domain Briefly.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.3 kB (31%)

Content Size

63.1 kB

After Optimization

43.8 kB

  • HTML
  • JavaScript

In fact, the total size of Briefly.app main page is 63.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 58.3 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.2 kB

  • Original 4.8 kB
  • After minification 4.8 kB
  • After compression 1.7 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 3.2 kB or 65% of the original size.

JavaScript Optimization

-28%

Potential reduce by 16.1 kB

  • Original 58.3 kB
  • After minification 58.3 kB
  • After compression 42.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 16.1 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (70%)

Requests Now

20

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Briefly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

briefly.app

briefly.app

205 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

47 ms

icon

icon

54 ms

quill.snow.css

quill.snow.css

105 ms

main.94c6de74.js

main.94c6de74.js

266 ms

main.79a7a339.css

main.79a7a339.css

191 ms

firebase-app.js

firebase-app.js

45 ms

firebase-analytics.js

firebase-analytics.js

47 ms

gtm.js

gtm.js

92 ms

hotjar-2676546.js

hotjar-2676546.js

125 ms

css2

css2

44 ms

insight.min.js

insight.min.js

68 ms

js

js

78 ms

fbevents.js

fbevents.js

35 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

32 ms

insight_tag_errors.gif

insight_tag_errors.gif

168 ms

js

js

85 ms

analytics.js

analytics.js

20 ms

collect

collect

12 ms

collect

collect

27 ms

ga-audiences

ga-audiences

71 ms

Accessibility Review

briefly.app accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

briefly.app best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

briefly.app SEO score

88

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Briefly.app can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Briefly.app main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

briefly.app

Open Graph description is not detected on the main page of Briefly. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: