7.5 sec in total
512 ms
5.9 sec
1 sec
Welcome to pages.fm homepage info - get ready to check Pages best content for Vietnam right away, or after learning these important things about pages.fm
Pancake - Omnichannel management platform - ALL-IN-ONE management solutions for selling on Facebook, Shopee, Lazada, TikTok, website...
Visit pages.fmWe analyzed Pages.fm page load time and found that the first response time was 512 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pages.fm performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value5.1 s
24/100
25%
Value11.6 s
4/100
10%
Value2,390 ms
5/100
30%
Value0.054
98/100
15%
Value31.4 s
0/100
10%
512 ms
1797 ms
1225 ms
744 ms
43 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 89% of them (67 requests) were addressed to the original Pages.fm, 8% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Pages.fm.
Page size can be reduced by 407.7 kB (72%)
567.1 kB
159.4 kB
In fact, the total size of Pages.fm main page is 567.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. 70% of websites need less resources to load. HTML takes 502.7 kB which makes up the majority of the site volume.
Potential reduce by 385.3 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 385.3 kB or 77% of the original size.
Potential reduce by 22.4 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. Obviously, Pages needs image optimization as it can save up to 22.4 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Number of requests can be reduced by 37 (56%)
66
29
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pages. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pages.fm
512 ms
pages.fm
1797 ms
antd.min.css
1225 ms
global.css
744 ms
css2
43 ms
new-pancake-etotalmarketing.svg
733 ms
VN_flag.svg
759 ms
messenger_icon.webp
762 ms
facebook_icon_v2.svg
770 ms
shopee_icon.svg
982 ms
customer_enagement.svg
990 ms
multipage_icon.svg
1010 ms
statistic_icon.svg
1016 ms
role_icon.svg
1027 ms
pos_integration_icon.svg
1377 ms
tools_bg_img1.webp
1517 ms
new_pancake_logo.svg
1377 ms
new_pos_logo.svg
1379 ms
botcake_logo.svg
1380 ms
new_store_cake_logo.svg
1463 ms
panchat_logo.webp
1516 ms
new_webcake_logo.svg
1564 ms
crm_logo.svg
1565 ms
new_pancake.png
1567 ms
meta_icon.png
1706 ms
fb_icon.svg
1732 ms
insta_icon.svg
1738 ms
twitter_icon.svg
1770 ms
linkedin_icon.svg
1780 ms
github_icon.svg
1799 ms
css2
22 ms
polyfills-5cec26be8c22cc84adfd.v3.js
1486 ms
webpack-d88fc55aaa492e999444.v3.js
1512 ms
framework.b5854cbc731fdd4279b2.v3.js
1714 ms
c553178f6fec5740a4fdffad828bad324c4058c4.37406443699ceff711c6.v3.js
1555 ms
main-8bc1ec0178d87eea02e5.v3.js
1567 ms
aec7d165.95ffd7d3ebad920a1dcf.v3.js
2354 ms
674a26a7.0b8dc79dac3733b62a68.v3.js
2228 ms
7479380b.86869b5971467bc2f948.v3.js
1782 ms
29107295.c2207fba7ed6e3ad79f4.v3.js
1812 ms
eb7a1b1d.06fd2be5cecf210ce4da.v3.js
1573 ms
68251c6f.18f32c00191bbee02fc5.v3.js
1954 ms
9384563a4f29b9a87449e54f151d4d68fb039dac.77d3f05992a305a599eb.v3.js
1771 ms
d7facbdc513005ecc72b5460c889bcdfdaf295d4.6752d79183b69a3b9acd.v3.js
1782 ms
16efd1ae47ba563110b8a9565a5d26636a4621bb.bd0c873dd69d794844b6.v3.js
1791 ms
416c3610eb800f72027a6e92fad4b73435bf690a.087b1945ee4dcefc1b0a.v3.js
1795 ms
e59fac9ad864198481b057631cd44edd51462953.f168b983e3b46f0b1c8d.v3.js
1808 ms
e430a00d550786b224267cecd33ac259e5098168.551f93499181c92601ca.v3.js
2569 ms
a07002bc0ecdeeaaa129796e99a5abd94b341b38.8ca735a92cc9c20bf52e.v3.js
1925 ms
e7decac1f50ee723da375d98ea5f141e4e5cd946.ceb34b44259bec6d8837.v3.js
1922 ms
6ab67e68317b3cc420cf019734cc6e0efadd8a24.8664d753dba1f52a6a62.v3.js
2434 ms
74ce6178519d13df402d846355358143563ab23e.e356d2761696a88e0740.v3.js
1676 ms
169290d762b2d46abd79da5c681adf7fbe1fc85b.fe15a1559c119096fdd7.v3.js
1708 ms
1e934b0678f88857cd0a64ec646816a99e6e1161.cde837bdca60bfc994ba.v3.js
1821 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf
22 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZg.ttf
82 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuOKfMZg.ttf
134 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuDyfMZg.ttf
135 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyeMZg.ttf
135 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuGKYMZg.ttf
135 ms
7b8d33123a126a862fbfcc1f35696cd79a1ec158.7a3dd688c6a2f5e40cea.v3.js
1817 ms
fe262a802b2e458b271b9548be53d60c99b1acab.ebe1e4451bddd31ef0be.v3.js
1859 ms
dc0f040076d1bd5e59f14f9fa4029ab04abb97ec.f5848694242bea3fca69.v3.js
1825 ms
573372f4083387f89da86be1189782825adc601d.7050a7f44eb96806e824.v3.js
1882 ms
_app-b5447c7c8971e6bb8612.v3.js
2161 ms
5ae20cb2f3447f1d3cca273bb29554f45041f472.83d6ed30e011dc4c3cca.v3.js
2011 ms
0af2298ae523b8b5b4ba8af00eaa5b92449f3f79.c8bf3a7a2b2f2d593b66.v3.js
2042 ms
b811bd40098fc41c35ff6fd2fe8642bba9b5f745.743c06b03fb3bf5c514e.v3.js
1985 ms
12e6b4cf24d1eedfe886082090870e96e1b7e937.e74eb3fe5690e04d7673.v3.js
2100 ms
index-6d8a3a7ae08ef6ea344b.v3.js
2103 ms
_buildManifest.js
2090 ms
_ssgManifest.js
2155 ms
Montserrat-Regular.ttf
2197 ms
download-on-app-store.png
2088 ms
download-on-google-play.png
2090 ms
pages.fm accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
pages.fm 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pages.fm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Pages.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 Pages.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.
pages.fm
Open Graph data is detected on the main page of Pages. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: