8.2 sec in total
504 ms
7.6 sec
133 ms
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
Bứt phá doanh thu với Pancake.vn - Phần mềm quản lý tương tác, khách hàng đa kênh, quản lý bán hàng online, tại quầy, tích hợp vận chuyển, tiện ích.
Visit pages.fmWe analyzed Pages.fm page load time and found that the first response time was 504 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pages.fm performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value21.7 s
0/100
25%
Value14.7 s
1/100
10%
Value16,780 ms
0/100
30%
Value0.311
38/100
15%
Value35.4 s
0/100
10%
504 ms
1708 ms
814 ms
916 ms
108 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 92% of them (84 requests) were addressed to the original Pages.fm, 7% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Pages.fm.
Page size can be reduced by 391.4 kB (55%)
717.0 kB
325.6 kB
In fact, the total size of Pages.fm main page is 717.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 379.2 kB which makes up the majority of the site volume.
Potential reduce by 261.9 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 261.9 kB or 78% of the original size.
Potential reduce by 129.5 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 129.5 kB or 34% 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 34 (43%)
79
45
The browser has sent 79 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 as a result speed up the page load time.
pages.fm
504 ms
pages.fm
1708 ms
antd.min.css
814 ms
global.css
916 ms
css2
108 ms
pancake_light.svg
880 ms
fold_icon.svg
937 ms
index_background.png
935 ms
Cart.svg
919 ms
Smile.svg
1062 ms
Popular.svg
1070 ms
Checking.svg
1171 ms
Messenger.svg
1168 ms
Instagram.svg
1166 ms
dot_icon.svg
1168 ms
macbookpro.svg
1621 ms
index_header_mask.png
1379 ms
fpt.svg
1710 ms
cocacola_logo.png
1718 ms
vtv_logo.png
1715 ms
elux_logo.svg
1446 ms
visa_logo.png
1657 ms
logo_auchan.png
1993 ms
mbb_logo.png
2157 ms
adayroi_logo.png
1935 ms
vtc_logo.png
2248 ms
topica_logo.png
2267 ms
elise_logo.png
1993 ms
yamaha_logo.png
2210 ms
nonson_logo.png
2254 ms
thanhnien_logo.png
2248 ms
mwc_logo.png
2408 ms
ancarat_logo.png
2465 ms
mac.svg
2511 ms
ellipse_2.svg
2519 ms
polygon.svg
2522 ms
facebook_icon.svg
2525 ms
messenger_icon.svg
2695 ms
polyfills-093a70749ba2995dff91.js
2543 ms
main-dfc41e323e2c0aa88edf.js
1944 ms
webpack-302f1c04f08867cfbae6.js
1918 ms
framework.25ff582a09b9f894e44f.js
2000 ms
aec7d165.e8656100933760849554.js
2567 ms
674a26a7.2c13f15cefd0481b902a.js
2088 ms
7479380b.a68a93febc8d90d7ef8d.js
2338 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf
64 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf
171 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf
199 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfMZg.ttf
201 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeMZg.ttf
248 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf
202 ms
eb7a1b1d.327ab40da9072b266113.js
2035 ms
commons.95221e4a9d1874fba6bd.js
2039 ms
a90de00480aa87505a56cc25ee3f975ae89c2e87.8665b0fafbd597167b66.js
2318 ms
957bc61ae9a6f429773cd0870bd6a7f9d24338c9.2fc8456b97d57c29502a.js
2132 ms
f25a80be2d1d74abc741a3227bbe951b1ca7ce21.94733ee5a6085fd5f2d4.js
2205 ms
9c4565fc751d1b9ff8a2c22fa37a81d3b7f531db.c5026ccf4b7ae2746c58.js
3042 ms
4baedfc591ed922d428548df718fc5697d86c7c6.ba12f51aa2cbcbebd1f0.js
2191 ms
c1c213a568a44dc2c361c949c5dd2439c5f3d5d1.914455edf6eb1c0303a4.js
2171 ms
1924275a122d755f18390712792c630bdfb53522.20496be14e911aeeaf64.js
2019 ms
64857cc0c8f55bcbbbd121a830cb50a039a1a497.6edc2dd6dacef86caf06.js
2103 ms
73b2fe83c402dce5aceaca1885617811bc4b51f7.dff12a6350990e366229.js
2052 ms
f616e02a82a358c206f38d1512c146c0878c4504.c412f27992b15fdfbc0b.js
2130 ms
34c45d49b734d5a103736d40d826b876208b9104.2fee576ff782120c75bf.js
2179 ms
ee9dc37f42352c2b279fbc43633793dcbb5c636d.162e38ecf717db55ae0d.js
2000 ms
469115b851f0567584cf18d95dfafe5066e40dbf.d24c4ed668f3477d4827.js
2047 ms
6de56f72e17ae9c0b620b90a1e094b13847c9946.0a7eda8545db80048ed5.js
2052 ms
fda4664f6fcbaad8d212627cf4be37046ed0c656.564006566499c1f9d0c1.js
1959 ms
28b61f20c989af0b485a1f1ebd1b52d2405ec900.08e16d6726fe33787175.js
1964 ms
8ac721b8c712442ae099745486a1bd7fecd72762.e84105d086c58b34294d.js
1962 ms
3db8c593c48af82464396e8cfa73f24055696219.45b6993e7f74071cf589.js
2876 ms
_app-818903b5e13291fd8da1.js
2629 ms
13e972d4397b4fb366db42e03968a18413341a9c.c7272ee73621e5b1d644.js
2118 ms
42e39cb4a75299670ed7b7577c865dfa7ee64da3.c8cba2989520d48dc3ca.js
2022 ms
08a506c305204a68a6589925241e4ca6ff956d5c.4dd157bfef99dbbe8d55.js
2010 ms
84493014e94fe1b0339db1d18a190b453226affa.05263869e79e12956b11.js
1950 ms
index-7a4fdfe5ae5fc5296065.js
2136 ms
_buildManifest.js
2182 ms
_ssgManifest.js
2213 ms
Montserrat-Bold.ttf
2580 ms
Montserrat-Medium.ttf
2189 ms
Montserrat-SemiBold.ttf
2473 ms
Montserrat-Regular.ttf
2241 ms
instagram_icon.svg
2259 ms
whatsapp_icon.svg
2240 ms
shopee.svg
2251 ms
lazada.svg
2301 ms
tokopedia.svg
2133 ms
pancake.svg
2199 ms
download-on-app-store.png
2193 ms
download-on-google-play.png
2110 ms
pages.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.
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
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
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
Links are not crawlable
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
VI
N/A
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 Vietnamese 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 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: