2.4 sec in total
137 ms
2.1 sec
205 ms
Welcome to profcardy.com homepage info - get ready to check Prof Cardy best content for Brazil right away, or after learning these important things about profcardy.com
Matemática com o Professor Cardy. Exercícios de Matemática resolvidos, simulados e desafios para você aprender e ir bem nos vestibulares e ENEM
Visit profcardy.comWe analyzed Profcardy.com page load time and found that the first response time was 137 ms and then it took 2.3 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.
profcardy.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value9.1 s
1/100
25%
Value9.1 s
14/100
10%
Value1,490 ms
14/100
30%
Value0.001
100/100
15%
Value19.1 s
3/100
10%
137 ms
24 ms
61 ms
107 ms
106 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 60% of them (65 requests) were addressed to the original Profcardy.com, 6% (7 requests) were made to Tpc.googlesyndication.com and 5% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (528 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 253.9 kB (16%)
1.6 MB
1.3 MB
In fact, the total size of Profcardy.com main page is 1.6 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 52.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 9.3 kB, which is 15% 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 52.3 kB or 83% of the original size.
Potential reduce by 7.3 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. Prof Cardy images are well optimized though.
Potential reduce by 165.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 165.5 kB or 14% of the original size.
Potential reduce by 28.8 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. Profcardy.com needs all CSS files to be minified and compressed as it can save up to 28.8 kB or 22% of the original size.
Number of requests can be reduced by 80 (84%)
95
15
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prof Cardy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
profcardy.com
137 ms
css
24 ms
bootstrap.css
61 ms
font-awesome.min.css
107 ms
jslider.css
106 ms
settings.css
109 ms
jquery.fancybox.css
108 ms
animate.css
112 ms
video-js.min.css
114 ms
morris.css
158 ms
royalslider.css
160 ms
rs-minimal-white.css
159 ms
layerslider.css
162 ms
ladda.min.css
163 ms
datepicker.css
167 ms
jquery.scrollbar.css
211 ms
style.css
227 ms
pages.css
213 ms
pages-pages-customizer.css
211 ms
ie.css
214 ms
brand
11 ms
query_renderer.js
18 ms
js
19 ms
adsbygoogle.js
328 ms
jquery-2.1.3.min.js
223 ms
bootstrap.min.js
268 ms
jshashtable-2.1_src.js
267 ms
jquery.numberformatter-1.2.3.js
267 ms
tmpl.js
267 ms
jquery.dependClass-0.1.js
292 ms
draggable-0.1.js
293 ms
jquery.slider.js
316 ms
jquery.carouFredSel-6.2.1-packed.js
318 ms
jquery.touchwipe.min.js
320 ms
jquery.elevateZoom-3.0.8.min.js
317 ms
jquery.imagesloaded.min.js
370 ms
jquery.appear.js
371 ms
jquery.sparkline.min.js
373 ms
jquery.easypiechart.min.js
373 ms
jquery.easing.1.3.js
377 ms
jquery.fancybox.pack.js
376 ms
isotope.pkgd.min.js
382 ms
brandjs.js
19 ms
query_renderer.js
17 ms
js
112 ms
jquery.knob.js
323 ms
jquery.stellar.min.js
325 ms
jquery.selectBox.min.js
322 ms
jquery.royalslider.min.js
325 ms
jquery.tubular.1.0.js
320 ms
SmoothScroll.js
329 ms
country.js
329 ms
popularqueryjs
28 ms
spin.min.js
325 ms
ladda.min.js
332 ms
masonry.pkgd.min.js
323 ms
morris.min.js
323 ms
raphael.min.js
341 ms
video.js
334 ms
pixastic.custom.js
323 ms
livicons-1.4.min.js
437 ms
greensock.js
330 ms
layerslider.transitions.js
331 ms
layerslider.kreaturamedia.jquery.js
334 ms
counter.js
26 ms
jquery.themepunch.tools.min.js
297 ms
jquery.themepunch.revolution.min.js
323 ms
bootstrapValidator.min.js
334 ms
bootstrap-datepicker.js
346 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk37cxcABrE.ttf
25 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk3CstcABrE.ttf
26 ms
jquery.jplayer.min.js
346 ms
text.php
93 ms
jplayer.playlist.min.js
323 ms
jquery.scrollbar.min.js
350 ms
main.js
388 ms
fontawesome-webfont.woff
522 ms
logo-xx.png
522 ms
show_ads_impl.js
346 ms
iframe_api
47 ms
www-widgetapi.js
12 ms
ga.js
37 ms
__utm.gif
58 ms
zrt_lookup.html
62 ms
branding.png
48 ms
ads
474 ms
collect
32 ms
ads
345 ms
ga-audiences
61 ms
reactive_library.js
194 ms
ads
528 ms
3538642918446718525
167 ms
load_preloaded_resource.js
24 ms
abg_lite.js
21 ms
window_focus.js
120 ms
qs_click_protection.js
27 ms
ufs_web_display.js
7 ms
bbcd6bf18c20baa1b2adeb195de9b551.js
13 ms
fullscreen_api_adapter.js
115 ms
interstitial_ad_frame.js
153 ms
icon.png
13 ms
feedback_grey600_24dp.png
14 ms
settings_grey600_24dp.png
20 ms
css
63 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
17 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
20 ms
FAz5UgRug7M8YaGFfFWxr9vetrg5Yv9xXEx-zc6kZAs.js
4 ms
__utm.gif
6 ms
profcardy.com 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
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>).
profcardy.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
profcardy.com 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
Tap targets are not sized appropriately
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Profcardy.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Profcardy.com 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.
profcardy.com
Open Graph data is detected on the main page of Prof Cardy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: