8.9 sec in total
1 sec
5.8 sec
2.1 sec
Click here to check amazing Record content for Portugal. Otherwise, check out these important facts you probably never knew about record.pt
As grandes entrevistas, a melhor opinião e os conteúdos multimédia sobre futebol e todas as modalidades desportivas. As últimas notícias, reportagens, entrevistas, artigos desportivos, no Jornal Recor...
Visit record.ptWe analyzed Record.pt page load time and found that the first response time was 1 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
record.pt performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.5 s
1/100
25%
Value10.0 s
9/100
10%
Value2,800 ms
3/100
30%
Value0.096
91/100
15%
Value34.6 s
0/100
10%
1034 ms
841 ms
88 ms
566 ms
738 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 26% of them (35 requests) were addressed to the original Record.pt, 42% (56 requests) were made to Cdn.record.pt and 3% (4 requests) were made to Barra.xl.pt. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Record.pt.
Page size can be reduced by 708.5 kB (25%)
2.8 MB
2.1 MB
In fact, the total size of Record.pt main page is 2.8 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 520.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. This page needs HTML code to be minified as it can gain 100.5 kB, which is 17% 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 520.3 kB or 88% of the original size.
Potential reduce by 138.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. Record images are well optimized though.
Potential reduce by 49.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 122 B
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. Record.pt has all CSS files already compressed.
Number of requests can be reduced by 40 (32%)
126
86
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Record. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.record.pt
1034 ms
CofinaSSOInitScripts.js
841 ms
gtm.js
88 ms
smart-app-banner.min.css
566 ms
main.min.css
738 ms
homepage.min.css
700 ms
marcador_patrocinado.min.css
601 ms
header.js
889 ms
chartbeat_mab.js
33 ms
gpt.js
123 ms
HN8GJEAA.js
39 ms
pub-7994511480153112
82 ms
cofinahits.js
693 ms
homepage.js
2008 ms
hubs
1052 ms
board.js
54 ms
CofinaSSOApi.js
803 ms
fbevents.js
229 ms
pub-7994511480153112
190 ms
img_80x100$2024_05_09_00_55_50_2249810.jpg
929 ms
adServer.bs
416 ms
img_374x246%242024_05_09_12_38_52_715179.jpg
1122 ms
img_374x246%242024_05_03_16_16_48_456398.png
1058 ms
img_374x246$2024_04_18_17_11_08_1632085.jpg
1025 ms
img_374x246$2024_05_06_13_31_01_476625.jpg
1123 ms
img_80x100$2024_05_09_00_55_59_2249811.jpg
1025 ms
img_476x268$2024_05_09_19_04_42_2250009.png
1121 ms
img_476x268$2024_05_09_18_30_41_2249987.png
1263 ms
img_293x165$2024_05_09_20_05_54_2250030.png
1263 ms
img_293x165$2024_05_09_19_24_07_2250014.jpg
991 ms
img_293x165$2024_05_09_20_39_38_2250045.jpg
1056 ms
img_40x40$2024_05_09_18_58_30_2250005.png
1120 ms
img_40x40$2024_04_16_20_05_23_2242022.png
1156 ms
img_84x84$2015_11_04_18_38_16_1007025.png
1187 ms
img_84x84$2016_04_23_14_23_49_1093164.png
1262 ms
img_84x84$2024_04_19_15_59_05_2242887.png
1261 ms
img_84x84$2015_10_23_16_04_00_1006328.png
1298 ms
img_84x84$2015_11_05_10_19_20_1007060.png
1314 ms
img_84x84$2024_05_09_18_58_30_2250005.png
1649 ms
img_84x84$2024_04_16_20_05_23_2242022.png
1419 ms
img_84x84$2015_10_23_16_42_08_1006428.png
1415 ms
img_84x84$2015_10_23_16_01_19_1006316.png
1413 ms
img_84x84$2015_11_04_18_35_45_1007019.png
1461 ms
img_40x40$2015_10_23_16_42_08_1006428.png
1473 ms
img_40x40$2015_10_23_16_01_19_1006316.png
1648 ms
img_40x40$2015_10_23_16_04_00_1006328.png
1648 ms
img_40x40$2015_11_05_10_19_20_1007060.png
1647 ms
img_84x84$2015_11_20_13_50_21_1007527.png
1687 ms
img_84x84$2018_08_06_01_40_09_1432335.png
1688 ms
img_84x84$2015_11_20_13_45_29_1007524.png
1819 ms
img_84x84$2015_10_05_13_31_35_1005638.png
1826 ms
img_84x84$2016_07_22_19_39_55_1133569.png
1827 ms
img_84x84$2021_01_11_16_27_17_1801674.png
1827 ms
img_84x84$2015_10_05_13_35_48_1005645.png
1840 ms
img_84x84$2015_10_05_13_24_31_1005629.png
1839 ms
img_84x84$2015_10_05_13_26_31_1005632.png
1929 ms
img_84x84$2015_10_05_13_25_42_1005630_im_637954276383147872.png
1931 ms
img_84x84$2021_08_28_02_06_30_1896284.png
1924 ms
img_84x84$2015_11_19_19_38_16_1007504.png
1921 ms
img_84x84$2022_08_09_16_31_34_2027288.png
1985 ms
lg_print.png
589 ms
img_84x84_defaultTeam.png
852 ms
logoesc.png
853 ms
lpassin.png
852 ms
betano.png
851 ms
indicar.svg
1300 ms
pubads_impl.js
174 ms
record.html
1074 ms
agwrusgrw1
354 ms
ebx.js
352 ms
75.svg
1337 ms
grass_texture.jpg
2136 ms
ic_slb.svg
1683 ms
ic_fcp.svg
1982 ms
ic_scp.svg
2048 ms
ic_whatsapp.svg
2422 ms
diretos_esc_bg.jpg
1960 ms
bloco_p01.jpg
2206 ms
Rubik-Regular.woff
2894 ms
icomoon.woff
2730 ms
Rubik-Medium.woff
2988 ms
Rubik-Light.woff
3038 ms
new_capa_bg.jpg
2896 ms
1856755334598402
209 ms
podcasts_header_mobile.jpg
2939 ms
Teko-Light.woff
3152 ms
Teko-Regular.woff
3065 ms
header_np.png
2908 ms
logo-CStudio-dark.svg
2919 ms
clarity.js
20 ms
indica_bg.svg
3170 ms
livro_reclamacoes_preto.png
3111 ms
img_84x84$2015_10_05_13_35_14_1005643.png
1063 ms
img_84x84$2015_10_05_13_21_02_1005627.png
1075 ms
img_84x84$2015_10_05_13_37_53_1005652.png
1045 ms
img_84x84$2015_10_05_13_23_45_1005628.png
1028 ms
img_84x84$2015_10_05_13_36_40_1005647.png
965 ms
img_195x246$2024_05_09_00_55_50_2249810.jpg
1140 ms
jquery-1.10.2.min.js
316 ms
barracofina.css
526 ms
img_195x246$2024_05_09_00_55_59_2249811.jpg
1122 ms
img_80x80$2020_02_13_19_45_22_1663516.png
1018 ms
img_80x80$2016_08_29_16_51_14_1150152_im_636692415676719859.png
949 ms
img_80x80$2017_07_07_16_32_51_1286834_im_636692418571201221.png
973 ms
img_80x80$2015_10_12_13_07_15_1005695_im_636692412932370355.png
972 ms
img_374x246$2024_04_19_11_36_22_2242852.jpg
1216 ms
img_374x246$2024_03_07_21_04_52_2228965.jpg
1224 ms
img_374x246$2024_05_09_13_41_50_2249927.jpg
1208 ms
products.js
77 ms
containr.js
249 ms
uwt.js
76 ms
web_surveys.js
91 ms
img_374x246$2024_05_08_14_03_21_2249604.jpg
1112 ms
img_374x246$2024_05_07_10_05_35_2249160.jpg
1114 ms
js
68 ms
img_374x246$2024_05_06_13_37_19_2248854.jpg
1119 ms
analytics.js
193 ms
img_374x246$2024_05_03_10_31_06_2247551.jpg
1283 ms
img_374x246$2024_05_02_13_44_37_2247328.jpg
1322 ms
adsct
331 ms
adsct
342 ms
fonts.css
190 ms
widget_core-23.2.0.js
325 ms
img_40x40$2024_05_04_18_49_31_2248020.png
1024 ms
learn
280 ms
collect
23 ms
collect
54 ms
activity
260 ms
ga.js
170 ms
medialivre.png
155 ms
ga-audiences
183 ms
__utm.gif
12 ms
c.gif
8 ms
record.pt 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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
Links do not have a discernible 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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
record.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
record.pt 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Record.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Record.pt 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.
record.pt
Open Graph data is detected on the main page of Record. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: