1.6 sec in total
132 ms
633 ms
802 ms
Visit per.fm now to see the best up-to-date Per content and also check out these interesting facts you probably never knew about per.fm
HubSpot's CRM platform contains the marketing, sales, service, operations, and website-building software you need to grow your business.
Visit per.fmWe analyzed Per.fm page load time and found that the first response time was 132 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
per.fm performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value2.9 s
80/100
25%
Value3.8 s
84/100
10%
Value2,240 ms
6/100
30%
Value0.014
100/100
15%
Value15.3 s
7/100
10%
132 ms
50 ms
114 ms
114 ms
133 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Per.fm, 31% (11 requests) were made to Cdn2.hubspot.net and 20% (7 requests) were made to 53.fs1.hubspotusercontent-na1.net. The less responsive or slowest element that took the longest time to load (225 ms) relates to the external source Cdn2.hubspot.net.
Page size can be reduced by 152.8 kB (41%)
376.2 kB
223.4 kB
In fact, the total size of Per.fm main page is 376.2 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. 40% of websites need less resources to load. HTML takes 180.4 kB which makes up the majority of the site volume.
Potential reduce by 141.4 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. This page needs HTML code to be minified as it can gain 24.0 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 141.4 kB or 78% of the original size.
Potential reduce by 10.1 kB
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. Per images are well optimized though.
Potential reduce by 105 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.
Potential reduce by 1.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Per.fm has all CSS files already compressed.
Number of requests can be reduced by 16 (48%)
33
17
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Per. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.hubspot.com
132 ms
styles.css
50 ms
module_39963105441_promoBar.min.css
114 ms
button.min.css
114 ms
module_66945685888_WTM_-_Homepage_-_Branding_Rollout_Hero.min.css
133 ms
module_32625700689_WTM_-_Homepage_-_Products.min.css
111 ms
module_32625894188_WTM_-_Homepage_-_Community.min.css
107 ms
module_32625908550_WTM_-_Homepage_-_Customers.min.css
130 ms
10031559-1003891.js
134 ms
scripts.js
62 ms
project.js
76 ms
module_66945685888_WTM_-_Homepage_-_Branding_Rollout_Hero.min.js
124 ms
module_32625700689_WTM_-_Homepage_-_Products.min.js
125 ms
module_32625894188_WTM_-_Homepage_-_Community.min.js
123 ms
module_32625908550_WTM_-_Homepage_-_Customers.min.js
221 ms
index.js
74 ms
referral.js
121 ms
bundle.min.js
76 ms
scripts.min.js
225 ms
Search%20Icon.svg
138 ms
SUI-Homepage-Header-Desktop@2x.png
112 ms
SUI-Homepage-Header-Mobile@2x.png
93 ms
MarketingHub_Icon_Gradient_RGB_24px.svg
81 ms
SalesHub_Icon_Gradient_RGB_24px.svg
85 ms
ServiceHub_Icon_Gradient_RGB_24px.svg
86 ms
CMSHub_Icon_Gradient_RGB_24px.svg
86 ms
OperationsHub_Icon_Gradient_RGB_24px.svg
119 ms
Wordmark-White.svg
104 ms
1-icon.svg
96 ms
2-icon.svg
115 ms
3-icon.svg
199 ms
4-icon.svg
115 ms
app%20store%20high%20res.png
111 ms
google%20play%20high%20res.png
114 ms
hsg-icons.woff
59 ms
per.fm accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
per.fm best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
per.fm SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Per.fm 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 Per.fm 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.
per.fm
Open Graph data is detected on the main page of Per. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: