4.1 sec in total
46 ms
2.6 sec
1.5 sec
Click here to check amazing Pencilcase Blog content for United States. Otherwise, check out these important facts you probably never knew about pencilcaseblog.com
The Pencilcase Blog provides you with reviews on the best Fountain pens, pencils, pens, inks and paper!
Visit pencilcaseblog.comWe analyzed Pencilcaseblog.com page load time and found that the first response time was 46 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pencilcaseblog.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value4.0 s
49/100
25%
Value2.8 s
95/100
10%
Value60 ms
100/100
30%
Value0.141
78/100
15%
Value4.1 s
86/100
10%
46 ms
164 ms
125 ms
23 ms
122 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Pencilcaseblog.com, 60% (32 requests) were made to Blogger.googleusercontent.com and 11% (6 requests) were made to Blogger.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Blogger.googleusercontent.com.
Page size can be reduced by 106.4 kB (5%)
2.3 MB
2.2 MB
In fact, the total size of Pencilcaseblog.com main page is 2.3 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. 25% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 76.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 76.3 kB or 74% of the original size.
Potential reduce by 29.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. Pencilcase Blog images are well optimized though.
Potential reduce by 784 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 2 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. Pencilcaseblog.com has all CSS files already compressed.
Number of requests can be reduced by 7 (15%)
48
41
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pencilcase Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pencilcaseblog.com
46 ms
www.pencilcaseblog.com
164 ms
www.pencilcaseblog.com
125 ms
3566091532-css_bundle_v2.css
23 ms
addthis_widget.js
122 ms
jquery-latest.js
19 ms
3717461131-widgets.js
58 ms
analytics.js
107 ms
IMG_003-04-01.jpeg
224 ms
_DSF1335.jpg
487 ms
ENSSO%2BLOGO%2B2020.png
266 ms
PENWORLD%2BLOGO%2B2020.png
247 ms
STILOGRAFICA%2BLOGO%2B2020%2B2.png
389 ms
APPELBOOM%2BLOGO%2B2020.png
360 ms
SFPG%2BLOGO%2B2020%2B2.png
360 ms
_DSF1376.jpg
489 ms
_DSF1379.jpg
449 ms
_DSF1386.jpg
363 ms
_DSF1337.jpg
326 ms
_DSF1348.jpg
539 ms
_DSF1360.jpg
738 ms
_DSF1362.jpg
701 ms
_DSF1354.jpg
748 ms
_DSF1355.jpg
731 ms
BleedthroughAjotopocketpaper.jpg
710 ms
NamisuNovaStudio2023_-15.jpg
829 ms
NamisuNovaStudio2023_-24.jpg
1001 ms
NamisuNovaStudio2023_-19.jpg
1004 ms
NamisuNovaStudio2023_-05.jpg
1159 ms
NamisuNovaStudio2023_-28.jpg
1197 ms
NamisuNovaStudio2023_-18.jpg
1090 ms
NamisuNovaStudio2023_-25.jpg
1058 ms
NamisuNovaStudio2023_-22.jpg
1294 ms
NamisuNovaStudio2023_-16.jpg
1330 ms
AGalenMagnumOpus_013.jpg
1334 ms
AGalenMagnumOpus_016.jpg
1596 ms
galensizecomp.jpg
1601 ms
AGalenMagnumOpus_001.jpg
1558 ms
AGalenMagnumOpus_017.jpg
1793 ms
AGalenMagnumOpus_015.jpg
1765 ms
AGalenMagnumOpus_020.jpg
1659 ms
AGalenMagnumOpus_008.jpg
1957 ms
AGalenMagnumOpus_018.jpg
1966 ms
AGalenMagnumOpus_005.jpg
2034 ms
AGalenMagnumOpus_002.jpg
1965 ms
AGalenMagnumOpus_009.jpg
2138 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
86 ms
jizaRExUiTo99u79P0U.ttf
39 ms
authorization.css
35 ms
collect
14 ms
authorization.css
69 ms
13464135-lightbox_bundle.css
3 ms
1137035824-lbx.js
9 ms
pencilcaseblog.com accessibility score
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pencilcaseblog.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
pencilcaseblog.com SEO score
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pencilcaseblog.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Pencilcaseblog.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.
pencilcaseblog.com
Open Graph data is detected on the main page of Pencilcase Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: