2.5 sec in total
144 ms
1.4 sec
965 ms
Welcome to frill.co homepage info - get ready to check Frill best content for India right away, or after learning these important things about frill.co
Frill helps you collect and organize feature requests to better understand customer needs and prioritize your roadmap.
Visit frill.coWe analyzed Frill.co page load time and found that the first response time was 144 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
frill.co performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value16.4 s
0/100
25%
Value6.2 s
43/100
10%
Value3,450 ms
2/100
30%
Value0.109
87/100
15%
Value17.7 s
4/100
10%
144 ms
373 ms
51 ms
49 ms
18 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 76% of them (44 requests) were addressed to the original Frill.co, 10% (6 requests) were made to Images.ctfassets.net and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (673 ms) belongs to the original domain Frill.co.
Page size can be reduced by 57.1 kB (5%)
1.1 MB
1.1 MB
In fact, the total size of Frill.co main page is 1.1 MB. 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. Images take 961.0 kB which makes up the majority of the site volume.
Potential reduce by 57.0 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 57.0 kB or 74% of the original size.
Potential reduce by 5 B
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Frill images are well optimized though.
Potential reduce by 146 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 18 (35%)
52
34
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frill. 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 as a result speed up the page load time.
frill.co
144 ms
frill.co
373 ms
f7145a7f7d15e994c14f4c7c.js
51 ms
lib.js
49 ms
plausible.js
18 ms
3c450dd8cc8d3edac2a6.css
146 ms
2fdea4d1fb89c4c5fcde.css
151 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
337 ms
webpack-613fd858cdb9cf2af3be.js
219 ms
framework-e8d56eb39be14c9c4598.js
381 ms
main-011e14431c997dd5213e.js
374 ms
_app-6fad60ce1354e6b23cf0.js
553 ms
index-751dfb4814ca8239cb22.js
216 ms
_buildManifest.js
371 ms
_ssgManifest.js
374 ms
widget.js
519 ms
log
514 ms
niz-new.jpg
42 ms
eric-new.jpg
30 ms
Anika.jpg
32 ms
andrei.jpg
33 ms
Sam_H.jpg
33 ms
vaibhav-new.jpg
34 ms
redbull.svg
236 ms
orange.svg
238 ms
canary.svg
275 ms
land-book.svg
276 ms
dash.svg
281 ms
zion.svg
282 ms
superlist.svg
283 ms
acme-dashboard-lg.png
587 ms
trustpilot.svg
377 ms
capterra.svg
385 ms
g2.svg
382 ms
frill-widget-lg.png
416 ms
ideas.jpg
582 ms
roadmap.jpg
586 ms
frill-idea-matrix.png
472 ms
announcements.jpg
463 ms
slack.svg
474 ms
jira.svg
528 ms
trello.svg
538 ms
zendesk.svg
540 ms
intercom.svg
593 ms
helpscout.svg
601 ms
zapier.svg
604 ms
docs.svg
671 ms
sheets.svg
673 ms
monday.svg
651 ms
miro.svg
665 ms
azure.svg
652 ms
linear.svg
637 ms
asana.svg
641 ms
basecamp.svg
506 ms
airtable.svg
507 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZs.woff
68 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZs.woff
143 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZs.woff
148 ms
frill.co accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
frill.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
frill.co SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frill.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Frill.co 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.
frill.co
Open Graph data is detected on the main page of Frill. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: